;; ;; Licensed to the Apache Software Foundation (ASF) under one ;; or more contributor license agreements. See the NOTICE file ;; distributed with this work for additional information ;; regarding copyright ownership. The ASF licenses this file ;; to you under the Apache License, Version 2.0 (the ;; “License”); you may not use this file except in compliance ;; with the License. You may obtain a copy of the License at ;; ;; http://www.apache.org/licenses/LICENSE-2.0 ;; ;; Unless required by applicable law or agreed to in writing, ;; software distributed under the License is distributed on an ;; “AS IS” BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY ;; KIND, either express or implied. See the License for the ;; specific language governing permissions and limitations ;; under the License. ;;
The downloads on this page are from our current releases, produced as part of our community release process. In addition to the source artefacts below, Qpid is available via packages and Maven.
It is important to verify the integrity of the files you download.
Content | Version | Download | More |
---|---|---|---|
Qpid Proton | {{current_proton_release}} | Source (ASC, SHA512) | Release Page |
Qpid ProtonJ2 | {{current_protonj2_release}} | Source (ASC, SHA512), Binary (ASC, SHA512) | Release Page, Maven |
Qpid JMS (jakarta.jms) | {{current_jms_release}} | Source (ASC, SHA512), Binary (ASC, SHA512) | Release Page, Maven |
Qpid JMS (javax.jms) | {{other_jms_release}} | Source (ASC, SHA512), Binary (ASC, SHA512) | Release Page, Maven |
Qpid Proton-J | {{current_proton_j_release}} | Source (ASC, SHA512), Binary (ASC, SHA512) | Release Page, Maven |
Qpid Proton DotNet | {{current_proton_dotnet_release}} | Source (ASC, SHA512), Binary (ASC, SHA512) | Release Page |
Qpid JMS AMQP 0-x | {{current_jms_amqp_0_x_release}} | Source (ASC, SHA512), Binary (ASC, SHA512) | Release Page, Maven |
Qpid Messaging API C++ | {{current_cpp_release}} | Source (ASC, SHA512) | Release Page |
Qpid Messaging API Python 2* | {{current_python_release}} | Source (ASC, SHA512) | Release Page |
* Look to the newer Qpid Proton for Python 3 and AMQP 1.0 support.
Content | Version | Download | More |
---|---|---|---|
Broker-J | {{current_broker_j_release}} | Source (ASC, SHA512), Binary (ASC, SHA512) | Release Page |
C++ broker | {{current_cpp_release}} | Source (ASC, SHA512) | Release Page |
Dispatch router | {{current_dispatch_release}} | Source (ASC, SHA512) | Release Page |
Content | Version | Download | More |
---|---|---|---|
Qpid Interop Test | {{current_interop_test_release}} | Source (ASC, SHA512) | Release Page |
It is essential that you verify the integrity of the downloaded files using the ASC signatures or SHA checksums.
The signatures can be verified using PGP or GPG. First download the KEYS
file as well as the .asc
signature file for the relevant artefact. Then verify the signatures using one of the following sets of commands.
% gpg --import KEYS % gpg --verify <artifact-name>.asc <artifact-name> % pgpk -a KEYS % pgpv <artifact-name>.asc % pgp -ka KEYS % pgp <artifact-name>.asc
Alternatively, you can verify the SHA checksums of the files. Unix programs called sha1sum
and sha512sum
(or sha1
and sha512
) are included in many unix distributions. They are also available as part of GNU Coreutils. For Windows users, FSUM supports this. Ensure your generated checksum string matches the string published in the checksum file included with each release artefact.