Thanks for checking out Apache OODT. On this page you can download our official release.
N.B. OODT is ONLY released as source code and NOT binary. This is because you will most likely want to recompile various aspects of the codebase with configuration before deploying an OODT system.
See the 1.2.1-CHANGES.txt file for more information on the list of updates in this release.
OODT is always distributed under the Apache License, version 2.0.
You require Apache Maven to build the OODT source code. Maven can either be downloaded and installed manually or alternatively via command line via your operating system package manager.
FEB-2018: The Latest Apache™ OODT version 1.2.1 is now released and available for download.
The link in the Mirrors column below should display a default mirror selection based on your inferred location. If (when you browse to it) you do not see that page, try a different browser. The checksum and signature are links to the originals on the main distribution server.
|Version||Mirrors||MD5 Checksum||Signature||SHA Checksum|
|Apache OODT 1.2.1 (zip)||apache-oodt-1.2.1-src.zip||apache-oodt-1.2.1-src.zip.md5||apache-oodt-1.2.1-src.zip.asc||apache-oodt-1.2.1-src.zip.sha1|
It is essential that you verify the integrity of the downloaded files using the PGP, MD5 and/or SHA signatures. published with every OODT release.
Please read Verifying Apache HTTP Server Releases for more information on why you should verify our releases.
We strongly recommend you verify your downloads with at least both PGP and MD5. Guidance for doing so is provided below.
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.
N.B.Make sure you get these files from the main distribution directory, rather than from a mirror. Then verify the signatures using the following:
$ gpg --import KEYS $ gpg --verify apache-oodt-1.2.1-src.zip.asc
The files in the most recent release are signed by 2048R/0C1E654B Chris Mattmann (CODE SIGNING KEY - Apr 2016) <email@example.com> (CODE SIGNING KEY)
Alternatively, you can verify the MD5 signature on the files. A unix program called md5 or md5sum is included in many unix distributions.
$ md5sum apache-oodt-1.2.1-src.tar.gz
... output should match the string in apache-oodt-1.2.1-src.zip.md5