Use the links below to download a distribution of Apache OpenJPA. It is good practice to verify the integrity of the distribution files.
Official JPA 2.0 Releases¶
These releases implement the JSR-317 Java Persistence 2.0 specification and pass the JPA 2.0 TCK.
Official JPA 1.0 Releases¶
These releases implement the JSR-220 Java Persistence 1.0 specification and pass the Sun JPA 1.0b Technology Compatibility Kit.
Older incubating Releases¶
Verifying Release Version and Revision¶
OpenJPA jar is self-describing and after downloading a release, you can find out the revision number included in the build by:
% java -jar your/path/to/openjpa.jar
which will print the version and revision numbers, for example:
OpenJPA 2.1.0 version id: openjpa-2.1.0-r422266:1071315 Apache svn revision: 422266:1071315
which designates that the 2.1.0 release includes Apache SVN revision 1071315 as the latest.
We strongly recommend you verify the integrity of the downloaded files with both PGP and MD5. 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 one of the following sets of commands:
Verifying Release Files using the pgpk Utility¶
% pgpk -a KEYS % pgpv openjpa-*.zip.asc
Verifying Release Files using the pgp Utility¶
% pgp -ka KEYS % pgp openjpa-*.zip.asc
Verifying Release Files using the gpg Utility¶
% gpg --import KEYS % gpg --verify openjpa-*.zip.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 [here|http://www.fourmilab.ch/md5/] or here . fsum supports MD5 and SHA1.
(**) asm-3.2.jar can be found from http://search.maven.org/remotecontent?filepath=asm/asm/3.2/asm-3.2.jar .