Releasing OpenJPA has been edited by Marc Prud'hommeaux (Aug 29, 2007).

Change summary:

Updated release instructions to reflect new procedures

(View changes)


Making an OpenJPA Release

These instructions guide the release manager through the steps of making an official OpenJPA release.


  1. You should read the OpenJPA Release Policy to decide on the name of the new release, based on the content.
  2. You should read the Apache Release FAQ
  3. You must have shell access to
  4. You must have the following utilities installed on your local machine and available in your path:

Tasks that need to be performed for each release

In the examples below, it is assumed that the release name will be 1.0.1, and that the current checked-in version name is 1.0.1-SNAPSHOT and stored in the branch named 1.0.x.
Monday, 12:00 Make sure the One time setup steps have been performed
Monday, 12:01 Create a sub-branch off of the parent branch from which to make the release. Releasing from a branch will allow any cosmetic changes that need to be made for the release to be approved to be done without preventing other more disruptive advances in the trunk from potentially causing problems with the release. A branch can be made by running:
svn copy -m "OpenJPA Release 1.0.1 branch" \ \
Monday, 12:02 Check out a clean branch from which to build the release:
svn checkout
cd 1.0.1
Monday, 12:03 Update all the POMs to remove "-SNAPSHOT" suffix from the version. If you have perl installed, you can easily do it with a single command:
perl -pi -e "s;<version>1.0.1-SNAPSHOT</version>;<version>1.0.1</version>;g" pom.xml */pom.xml */*/pom.xml
Monday, 12:10 Verify that LICENSE.txt contains up to date licenses for any dependencies which are included in our distribution.
Any jars or source code which is included with the OpenJPA distribution that is not covered by the Apache license must be noted in LICENSE.txt. Two examples of this are the persistence and orm dtds (licensed under the CDDL) and Serp. If any new non Apache dependencies have been introduced they will have to be covered here as well. If any discrepancies are found update LICENSE.txt and commit the changes.
Monday, 12:15 Update BUILDING.txt, CHANGES.txt and RELEASE-NOTES.html
  • BUILDING.txt should be included in the source tarball and contains instructions on how to build OpenJPA. Prior to shipping a release we should ensure that those instructions are accurate.
  • CHANGES.txt contains a text representation of all the changes which have been made since the preceding release. Most of the contents of this file can be generated through JIRA's release notes mechanism here
  • RELEASE-NOTES.html contains general information on the OpenJPA project as well as an html version of the changes since the preceding version. The html change log may also be generated via JIRA.
Monday, 12:20 Commit the POM changes
svn commit -m "Updated to version 1.0.1 for the release"
Monday, 12:21 Perform an initial build and install it in the local repository (this step is only required because of an open bug with Maven's javadoc plugin):
mvn clean install -Dtest=false
Monday, 12:23 Now build the release locally, which will build and test, run the Apache Release Audit Tool to verify license headers, generate the javadoc and docbook PDF and HTML, run through the JPA TCK, build the source and binariy assemblies in target/site/downloads/, and sign the release files.
export MAVEN_OPTS=-Xmx1000m
mvn --batch-mode deploy site -Ptest-derby -Ptck-profile -Pexamples-profile \
    -Plicense-verify-profile -Pjavadoc-profile -Pdocbook-profile -Psign-release \
    -Djava14.jar=${JAVA_HOME}/../../1.4/Classes/classes.jar \${HOME}/.m2/privaterepos/

This operation will also sign the release files with the gpg utility using the <username> key. If your code signing key is under a different address, specify it by appending the following argument to the command above:

The java14.jar path should be changed to the local install path for the JDK 1.4 rt.jar so that JDK 1.4 verification can take place.

The path should be changed to the local install path to the JPA TCK so that the TCK can be run against the release.
Monday, 13:00 Verify the signatures:
gpg --multifile --verify target/site/downloads/*.asc
Monday, 13:01 Upload the release candidate to
mvn site:deploy

Bear in mind that uploads to are not visible at until after the hourly synchronization has taken place, as described at

Monday, 15:00 Start a vote for the release on the mailing list. Votes made by committers and members of the OpenJPA project are considered binding for this vote. For an example of the mail, see this archived 1.0.0 vote
Tuesday, Wednesday While waiting for the vote to complete, perform whatever manual review and testing on the release you deem appropriate.
Thursday, 15:00 If the vote is successful after 3 days tally the votes in an email to, like this one.
Thursday, 15:10 Make the OpenJPA assemblies available to the Apache mirroring system by copying them over on
cp -r /www/ /www/

The OpenJPA binary release will be available via the link after 24 hours, as per the Apache mirroring information.

Thursday, 15:15 Now that the release is locked down, convert the writeable 1.0.1 branch to a (du jure) read-only tag:
svn mv -m "OpenJPA Release 1.0.1 tag" \ \
Thursday, 15:16 Check out the parent branch and bump up the release number to be the next snapshot version:
svn checkout
cd 1.0.x
perl -pi -e "s;<version>1.0.1-SNAPSHOT</version>;<version>1.0.2-SNAPSHOT</version>;g" pom.xml */pom.xml */*/pom.xml
svn commit -m "Updating version in branch to 1.0.2-SNAPSHOT"
Thursday, 15:20 Update the page with links to the download mirrors, using the existing entries as templates.
All artifacts ( and must link to the mirrors, but signatures ( and must not link to mirrors.
Thursday, 15:30 The documentation on the server-side must manually be extracted on, and the links at need to be updated with the new versions and the "latest" documentation symbolic links need to be updated:
cd /www/
unzip downloads/
rm /www/
ln -fvs ../builds/1.0.1/apache-openjpa-1.0.1/docs/ /www/

Then point the links on to:
Thursday, 15:45 Merge the staged maven2 repository jars to with the official repository to rsync. This is currently a difficult process that requires the maven-staging-plugin, which much be built from source. The process looks something like this (executed in the root of your local OpenJPA checkout):
svn co /tmp/maven-stage-plugin
mvn -f /tmp/maven-stage-plugin/pom.xml clean install
find . \
    -name m2-repository -not -path "*openjpa-project*" \
    -exec mvn -f /tmp/maven-stage-plugin \
    stage:copy -Dsource=file://{} \
    -Dtarget=scp:// \
    -Dversion=1.0.1 \;

This process requires Maven 2.0.5. It is currently quite delicate and error-prone. Once the maven-stage-plugin is released, it should be possible to make it more automated.

Thursday, 16:00 Update the JIRA versions page to mark the version as "released", and set the date to the date that the release was approved. You may also need to make a new release entry for the subsequent release.
Friday, 16:00 After the mirrors have had time to update (24 hours to be on the safe side), make a news announcement on the OpenJPA wiki.
Once the news item is made, it won't show up on the front page unless you make some minor edit to the containing page (e.g., adding a newline somewhere).
Friday, 16:05 Make an announcement about the release on the list (and, for major releases, on the list as per the Apache Announcement Mailing Lists page). The announcement might look something like this.
Friday, 16:10 Make an announcement for the OpenJPA project (optional)
Friday, 17:00 Have a beer and enjoy your weekend while the world's grateful programmers revel in yet another high-quality release of Apache OpenJPA!

One time setup

These setup steps only need to be performed on a particular machine once.

Developers using Linux workstations can skip over the references to PuTTY and Cygwin

Create and install a SSH key

1 Install PuTTY
2 Use PuttyGen to create a SSH key (see Putty help for details)
3 Use PuTTY to ssh to
4 Create a ~/.ssh folder
5 pscp your SSH public key to ~/authorized_keys
6 ssh to
7 Create a ~\.ssh folder and move authorized_keys there
8 Configure putty to use your private key and save the session

Create a PGP key

1 Install cgywin, including utils/gpg
2 Generate a key with $ gpg --gen-key
3 Backup your cygwin home directory to another media
4 Add your key to

Update Maven settings for our servers

1 Create a settings.xml under .m2 (in your Document and Settings folder in Windows)
<settings xmlns=""

Expose a copy of known hosts to Maven

1 From cygwin, ssh to, save the public key if prompted, and exit
  cygwin will save the known hosts to your ~/.ssh folder, but the script cannot access it there (from Windows)
2 From cygwin (not Windows) create another .ssh folder at
3 Copy the known_hosts file to the new .ssh folder


Powered by Atlassian Confluence (Version: 2.2.9 Build:#527 Sep 07, 2006) - Bug/feature request

Unsubscribe or edit your notifications preferences