Developers Guide

Getting the source, Building the trunks

To get the source, build the trunks and get along with Maven, follow the instruction given in this page: AUG : 0.2. Building trunks

Versioning Scheme

The version number of ApacheDS has the following form:

<major>.<minor>.<micro> \[-M<milestone number> or -RC<release candidate number>]

This scheme has three number components:

  • The major number increases when there are incompatible changes in the API.
  • The minor number increases when a new feature is introduced.
  • The micro number increases when a bug or a trivial change is made.

and an optional label that indicates the maturity of a release:

  • M (Milestone) means the feature set can change at any time in the next milestone releases. The last milestone release becomes the first release candidate after a vote.
  • RC (Release Candidate) means the feature set is frozen and the next RC releases will focus on fixing problems unless there is a serious flaw in design. The last release candidate becomes the first GA release after a vote.
  • No label implies GA (General Availability), which means the release is stable enough and therefore ready for production environment.
A stable version is a version with a frozen set of features, and a frozen API. We don't release a version if all the integration tests are not passing, so any release should be considered stable enogh to be used.
Although we may add new features between two milestones, and the data structure may change, which may imply that the data have to be extracted and reimported in order for the server to be operational.
The configuration might also evolve between two versions.

Coding standards

The applicable coding standards for ADS 2.0 are described in Coding Standards

There are some more rules, as we are using Java 6 now :

  • Use generics as much as you can. Generic are a good way to avoid casting, and it enforce the usage of the correct type.
  • If you can avoid Iterators, do so. There is this cool construction with a for( Type t: ) : use it !
  • Use assert. It's usefull, especially instead of a bunch of if () then throw Exception* when controlling incoming parameters
  • Use the new Enum type !

Releasing ApacheDS

Here is a guide on how to cut a new release. This is a long process, expect it to last a few hours !

First, you need to have a recent version of Maven (we are using 3.0.4) and a recent version of the JDK (1.7 is ok, it should also build with 1.6).

Maven Settings

You'll need a settings section for the Nexus and servers with a password or a path to the SSH key used. Here's what my settings.xml file in ~/.m2 looks like:


    <!-- To publish a snapshot of some part of Maven -->

    <!-- To publish a website using Maven -->

    <!-- To stage a release of some part of Maven -->

    <!-- To stage a website of some part of Maven -->
      <id>stagingSite</id> <!-- must match hard-coded repository identifier in site:stage-deploy -->



      <!-- Configuration for artifacts signature -->


Just replace your username, passwords and paths. Note that the username and password is your Apache LDAP account.

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:

gpg --gen-key
gpg --fingerprint
gpg --keyserver --send-keys <your key's id from last command>
Make sure to have created the .pgpkey in your p.a.o/~ directory and to have added your public key to the KEYS file. See also

Releasing ApacheDS

Now that your environment has been setup, we will show you how to build and release the ApacheDS subproject. Keep an eye out for warnings and note sections that show version specific differences in this process.

Manual Steps

Some things have not yet been automated with maven and require users to manually edit some files. Below are the steps to follow.

Update the apacheds/pom.xml

The current apacheds/pom.xml contains references to LDAP API SNAPSHOTs, which is not good. You have to bump up those references to the latest LDAP-API version.

Update service/ and service/apacheds.bat

Edit the files in the service project directory to update the revision numbers used in that file to reference non-SNAPSHOT releases.

Release process

Since we are using Nexus for releases the release process is as follows (see also Publishing maven artifacts.

Test the Project
$ mvn release:prepare -DdryRun=true

Replace the version by the new version. Be careful, and remove the 'apacheds-parent-' which is proposed for the new tag. We should just use the version number.

Deploy a Snapshot
$ mvn deploy

This is useful to verify your settings in ~/.m2/settings.xml (Nexus password and GPG key)

Prepare the Release
$ mvn release:clean
$ mvn release:prepare

This creates a tag here

Stage the Release
$ mvn release:perform

This deploys the release to a staging repository. Go to Staging Repositories and close the staging repository.

Build the Site

We will now build the site. This will be done from the target/checkout directory :

$ cd target/checkout

In order to generate the site, you have to comment some modules in the apacheds pom.xml file :


Then you can start the maven command :

$ mvn site

This creates the site and the Javadocs.

Now, you have to sign the sources packages which are in apacheds/target/checkout/target. Use your PGP key ID (the pub key, 4096R/[XXXXXXX] where [XXXXXXX] is the key ID)

You can get the keys by typing :

gpg --list-keys

You can use this small script that does the job (copy-paste this code in a file named in your path) :


echo "PGP Key ID: "

echo "PGP Key Password: "
stty -echo
stty echo
echo ""

for FILE in $(find . -maxdepth 1 -not '(' -name "" -or -name ".*" -or -name "*.md5" -or -name "*.sha1" -or -name "*.asc" ')' -and -type f) ; do

    if [ -f "$FILE.asc" ]; then
        echo "Skipping: $FILE"

    echo -n "Signing: $FILE ... "

    # MD5
    if [ ! -f "$FILE.md5" ];
        openssl md5 < "$FILE" | cut "-d " -f2 > "$FILE.md5"
        echo "  - Generated '$FILE.md5'"
        echo "  - Skipped '$FILE.md5' (file already existing)"

    # SHA1
    if [ ! -f "$FILE.sha1" ];
        gpg -v --default-key "$DEFAULT_KEY" --print-md SHA1 "$FILE" > "$FILE".sha1
        echo "  - Generated '$FILE.sha1'"
        echo "  - Skipped '$FILE.sha1' (file already existing)"

    # ASC
    if [ ! -f "$FILE.asc" ];
        echo "$PASSWORD" | gpg --default-key "$DEFAULT_KEY" --detach-sign --armor --no-tty --yes --passphrase-fd 0 "$FILE"
        echo "  - Generated '$FILE.asc'"
        echo "  - Skipped '$FILE.asc' (file already existing)"

Then to sign the packages :

PGP Key ID: 
<your PGP key>
PGP Key Password: 
<Your password>

-n Signing: ./apacheds-parent-<version> ... 
- Generated './apacheds-parent-<version>'
- Generated './apacheds-parent-<version>'
- Generated './apacheds-parent-<version>'
Publish Source Distribution Package

The sources, binaries and their signatures, have to be pushed in a place where they can be downloaded by the other committers, in order to be chekced while validating the release. As the ~/ server is not anymore available for that purpose, we use the distribution space for that purpose.

If you haven't checked out this space, do it now :

$ mkdir -p ~/apacheds/dist/dev/directory
$ svn co ~/apacheds/dist/dev/directory

That will checkout the full project distributions.

You may want to checkout only the part that you are going to generate, to avoid getting Gb of data :

$ mkdir -p ~/apacheds/dist/dev/directory/apacheds
$ svn co ~/apacheds/dist/dev/directory/apacheds

Now, create a sub-directory for the version you have generated (here, for version 2.0.0-M22) :

$ mkdir ~/apacheds/dist/dev/directory/apacheds/2.0.0-M22

and copy the packages and signature to this area :

$ cd target/checkout/target
$ cp apacheds-parent-<version>* ~/apacheds/dist/dev/directory/apacheds/2.0.0-M22

Last, not least, commit your changes

$ svn add ~/apacheds/dist/dev/directory/apacheds/2.0.0-M22
$ svn ci ~/apacheds/dist/dev/directory/apacheds/2.0.0-M22 -m "ApacheDS 2.0.M22 packages"
Test the new version

The best way to do that is to download the sources, extract them, build the server and the installers, and check if the installers are correctly working. Then check that the server is correctly running.

Create the installers

We now have to create the installers. Go into the target/checkout directory and run :

$ cd apacheds/target/checkout/installers
$ mvn clean install -Pinstallers

This will create the installers in the target/checkout/installers/target/installers directory

We are meant to create all the installers. It's possible to create installers for a specific platform by using a different profile :
  • Debian : mvn clean install -Pdebian
  • Rpm : mvn clean install -Prpm
  • Windows : mvn clean install -Pwindows
  • Mac OS X : mvn clean install -Pmac
  • Binary : mvn clean install -Pbin
  • Archive : mvn clean install -Parchive
This will build only one single target.

Sign those installers using the script, and copy them in

$ cd apacheds/target/checkout/target/installers/target/installers
$ cp apacheds-<version>* ~/apacheds/dist/dev/directory/apacheds/2.0.0-M22

Note : you will need a Debian, a Fedora and a Windows server to generate dedicated binaries for those platforms, or you can use rpmbuild, dpkg or nsis if you don't want to use many different servers.


Start a 72h vote at the dev mailing list.


If the vote succeeds Apacheds project can be released.

Go to and release the staging repository so all artifacts are published to Maven central.

The sources, binaries and their signatures, have to be pushed in a place where they can be downloaded by users. We use the distribution space for that purpose.

Move the distribution packages (sources and binaries) to the dist SVN repository:$(version)

If you haven't checked out this space, do it now :

$ mkdir -p ~/apacheds/dist/release/directory
$ svn co ~/apacheds/dist/release/directory

That will checkout the full project distributions.

You may want to checkout only the part that you are going to generate, to avoid getting Gb of data :

$ mkdir -p ~/apacheds/dist/release/directory/apacheds/dist
$ svn co ~/apacheds/dist/release/directory/apacheds/dist

Then move the packages from 'dev' to 'release' :

# cd dist/release/directory/apacheds/dist
# cp ~/apacheds/dist/dev/directory/apacheds/<version> .
# svn add <version>
# svn ci <version>
# exit

The packages should now be available on

Deploy the Javadocs and XRef

We now can deploy the generated Javadoc and cross-reference pages. They are generated in the following directory :


We will copy two directories :


Staging or Production?

Those files will be stored on the production server only !!! And some extra caution must be taken not to delete them when we will publish the staging site too...

First of all, you must checkout the two CMS store for the site : staging and revision.

$ cd ~/apacheds
$ svn co staging
$ svn co production

Now, you will first add the directory for the newly generated version :

$ cd ~/apacheds/production/content/apacheds/gen-docs
$ mkdir <version>

Then copy the generated docs :

$ cp -r ~/apacheds/trunks/apacheds/target/checkout/target/site/apidocs ~/apacheds/production/content/apacheds/gen-docs/<version>
$ cp -r ~/apacheds/trunks/apacheds/target/checkout/target/site/xref ~/apacheds/production/content/apacheds/gen-docs/<version>

You have to check in those directories :

$ svn add <version>
$ svn ci <version> -m "Injected <version> javadocs"

Now, you have to update the staging site, but first, do a svn up. the you have to update the extpaths.txt file.

This file list the file on the production site that will not be overriden by the publication of the staging site. It has to be updated

$ cd ~/apacheds/staging/content/
$ vi extpaths.txt

Add the following line :

# Apacheds

then save and check in the file.

We also have to update the .htaccess file :

$ cd ~/apacheds/staging/content/apacheds/gen-docs
$ vi .htaccess

And update the two last lines to refer to the version you've just released :

RewriteRule ^latest$ <version>/
RewriteRule ^latest/(.*)$ <version>/$1

Save and commit the file.

Update the web site

You can now update the site, add a news on the front page, and publish the site.

There are a few places to modify :

  • /lib/ : update the $version_apacheds variable with the new version.
  • /content/index.mdtext : same here, update the section, which contains the version.
  • /content/apacheds/news.mdtext : add the news on top of thise page
  • /content/apacheds/download-old-versions.mdtext : add a new line on top of the array, which refers to the latest version before the new one

Commit the changes, and publish the web site, you are done !

Inform the world !

After 24h, you can now inform the world about the release.

Send a mail to the users and dev mailing list, and one to the

You are done !