Use the links below to download the Apache Flex® Blaze DS from one of our mirrors. You must verify the integrity of the downloaded files using signatures downloaded from this page.
Only current recommended releases are available on the main distribution site and its mirrors.
Please review the release notes before installing or compiling this testing suite.
The Apache Flex team is pleased to offer this release, available as of the 31th of March 2017. We welcome feedback and contributions to it from the wider Apache Flex community.
Please be aware of the dependencies listed in the section below. They are required in order to compile BlazeDS. The README explains these requirements further.
Convenience binary releases are not currently available for download from Apache.
Apache Flex Blaze DS requires some build tools which must be installed prior to building BlazeDS.
Apache relies on 3rd party mirrors to distribute their software. Because these releases are hosted on servers that are not under our control, we strongly recommend that you verify the integrity of the binaries or source code before you install it using the PGP or MD5 signatures listed next to the downloads. This involves a few extra steps, but it will verify that you are getting a true Apache release.
The PGP signatures can be verified using PGP or GPG. First download the KEYS as well as the asc signature file for the relevant distribution. Make sure you get these files as linked from this page (rather than a mirror) to insure the integrity of the files.
% pgpk -a KEYS % pgpv blazeds-4.7.3-source-release.tar.gz.asc
% pgp -ka KEYS % pgp blazeds-4.7.3-source-release.tar.gz.asc
% gpg --import KEYS % gpg --verify blazeds-4.7.3-source-release.tar.gz.asc
Alternatively, you can verify the MD5 signature on the files. A unix/Mac program called
md5sum is included in many unix distributions. It is also available as part of GNU Textutils. Windows users can get binary md5 programs from here , here , or here. An MD5 signature consists of 32 hex characters, and a SHA1 signature consists of 40 hex characters. Ensure your generated signature string matches the signature string published in the files above.