Releasing Apache Directory Projects can be involved. This release guide will walk you through the process first by preparing your maven and gpg configuration then by leading you through the release of various subprojects at Directory.
There may be a few things you'll need to setup before you can release. This release guide is geared to work off of a UNIX based system that has gpg installed. If you're using Windows then I feel for you .
We use Maven version 2.0.9 and JDK 1.5.0 (update 11) to build all Directory subrojects even if they run on JDK 1.4.2. If you build with JDK 1.4.2 you're build lamn versions of ApacheDS for example because certain optional functionality present when run on JDK 1.5.x and up will not be present.
Because of bugs in Maven SSH functionality that require 1.5.x you'll need to set the release.altDeploymentRepository property in the settings.xml (see below) to be able to deploy with Maven using JDK 1.6.x.
You'll need a settings section for the people.apache.org server with a password or a path to the SSH key used. Here's what my settings.xml file in ~/.m2 looks like:
Just replace your username in place of 'akarasulu' and if you're using a password replace the <privateKey> tag with <password> and add your UNIX account password there. Note that the username and password are the ones you use for your Apache UNIX account.
Syntax for altDeploymentRepository property can be found at http://maven.apache.org/plugins/maven-deploy-plugin/deploy-mojo.html. The altDeploymentRepository id and the server id must match.
You'll need to provide the passphrase in the settings.xml to access the gpg secret key installed on your host. This is due to a bug with the passphrase prompt in the maven-gpg-plugin. So unfortunately we must provide the passphrase in the settings.xml file in clear text. This should change in the future when this bug is fixed. Note that this passphrase is put into the release profile which we activate to properly sign and release the artifacts and poms via the release plugin.
All subprojects are configured to deploy signatures for the artifacts uploaded to the repository. The gpg plugin will check use the default gpg key for the user deploying the project with the release:perform directive of the release plugin. This will prompt you for the passphrase for the default key. If you do not have one setup the build will fail.
You can generate and upload a PGP key to a PGP keyserver using the following commands:
|Releasing Shared||Releasing Shared|
|Releasing Daemon||Releasing Daemon|
|Releasing ApacheDS||Releasing ApacheDS|
|Releasing Studio||Releasing Studio|
|Releases Announcements||Release Announcements|
Promoted by third party (update information may need to be sent)
|Studio||Open Source Rich client platform (RCP) email@example.com|