  |
|
Use the links below to download Apache JDO from one of our mirrors. For more information about the projects see Downloads. For information on running the TCK, see TCK.
It is good practice to verify the integrity of the distribution files.
You are currently using http://www.bizdirusa.com/mirrors/apache. If you encounter a problem with this mirror, then please select another. If all mirrors are failing, there are backup mirrors at the end of the list. See status of mirrors.
The api2 project contains source to build jdo.jar, which defines the JDO API version 2. The jar file is the only artifact needed for users who wish to compile their programs using the JDO 2 API. It can be downloaded automatically by maven and placed into the local maven repository if you include the proper dependency in your maven project definition. Use groupId javax.jdo, artifactId jdo2-api, version 2.1.1 and define your remote repository as http://www.ibiblio.org/maven. Alternatively, it can be downloaded manually and put into a location of your choice.
jdo2-api-2.1.1.jar [PGP] [MD5]
jdo2-api-2.1.1.pom [PGP] [MD5]
This is a download for all implementors of JDO, and for those who want to check how well an implementation is compliant with the JDO specification. The tck2 project contains the JDO 2 Technology Compatibility Kit. The source distribution is the only artifact needed to be downloaded by the user. The dependencies (including the model20 jar, util20 jar, enhancer20 jar, api2 jar, and JPOX) are automatically downloaded by maven as needed to run the TCK.
The enhancer20 project contains utility classes the tck uses for verifying enhanced files.
jdo2-enhancer-2.1.1.jar [PGP] [MD5]
jdo2-enhancer-2.1.1.pom [PGP] [MD5]
The model20 project contains the JDO2 metadata model the tck uses.
jdo2-model-2.1.1.jar [PGP] [MD5]
jdo2-model-2.1.1.pom [PGP] [MD5]
The util project contains utility classes on which the tck project depends.
jdo2-util-2.1.1.jar [PGP] [MD5]
jdo2-util-2.1.1.pom [PGP] [MD5]
It is essential that you verify the integrity of the downloaded files using the PGP signature and/or the MD5 checksum. The checksum is not as strong an indicator as the PGP signature is.
The PGP signatures can be verified using PGP or GPG.
First download the KEYS
as well as the asc signature file for the particular
distribution.
Make sure you get these files from the
main distribution
directory, rather than from a mirror. Then verify the signatures using
% pgpk -a KEYS
or
% pgpv release_name.tar.gz.asc
% pgp -ka KEYS
or
% pgp release_name.tar.gz.asc
% gpg --import KEYS
% gpg --verify release_name.tar.gz.asc
Alternatively, you can verify the checksums on the files. Unix
programs called md5/sha1 or
md5sum/sha1sum are included in many unix
distributions. *sum is also available as part of
GNU Textutils.
Windows users can get binary md5 programs from http://www.fourmilab.ch/md5 and
hhttp://www.pc-tools.net/win32/freeware/console.
Windows SlavaSoft fsum supports MD5 and
SHA1.
We highly recommend verifying the PGP signature, though.
 |