0.2. Building trunks has been edited by Emmanuel Lécharny (Mar 05, 2009).

(View changes)

Work in progress

This site is in the process of being reviewed and updated.

This page give some information about the layout of Apache DS 1.5 trunks, and try to explain how it is built.

Project Hierarchy

The actual project hierarchy is the following (as of 1.5.4-SNAPSHOT) :

  • apacheds
    • apacheds-jdbm
    • bootstrap-extract
    • bootstrap-partition
    • bootstrap-plugin
    • btree-base
    • core
    • core-avl
    • core-constants
    • core-cursor
    • core-entry
    • core-integ
    • core-jndi
    • core-plugin
    • core-shared
    • core-splay
    • core-unit
    • interceptor-kerberos
    • jdbm-store
    • kerberos-shared
    • mitosis
    • protocol-changepw
    • protocol-dhcp
    • protocol-dns
    • protocol-kerberos
    • protocol-newldap
    • protocol-ntp
    • protocol-shared
    • schema-bootstrap
    • schema-extras
    • schema-registries
    • server-integ
    • server-jndi
    • server-replication
    • server-tools
    • server-unit
    • server-xml
    • utils
    • xbean-spring
    • xdbm-search
    • xdbm-tools
  • shared
    • asn1
    • asn1-codec
    • bouncycastle-reduced
    • convert
    • ldap
    • ldap-constants
    • ldap-jndi
  • daemon
    • bootstrappers
    • plugin

This hierarchy represent the projects being built. Some project (OSGI, ...) are not built

Prerequisites for building

You must have installed Maven 2.0.9 and have a JDK 5 installed on your computer. A working internet connection is also mandatory.


Download and install Maven 2.0.9. (ATTENTION !!! Do NOT use another version of Maven )

Add a MAVEN_HOME environment variable and add MAVEN_HOME/bin to your system path:

On a Linux box you could add the following to the .bashrc file (.bashrc is a file you'll find in your home directory)

export MAVEN_HOME=/opt/maven-2.0.9

Windows users, use Control Panel -> System -> Advanced -> Environment Variables



There may be some issues with older JDK versions and Kerberos, therefore we recommend using a version >=1.5.0_09

Getting the code

To download the sources, you must have installed a Subversion client.

With readonly access :

svn co http://svn.apache.org/repos/asf/directory/apacheds/trunk-with-dependencies/ apacheds-trunk

With read/write access (for committers only) :

svn co https://svn.apache.org/repos/asf/directory/apacheds/trunk-with-dependencies/ apacheds-trunk

Building the trunks

Enabling Snapshot Repositories

The following information is only needed if one want to setup its own maven repo. There is no need to define a settings.xml file for generic usage.
Before building the trunks, you must configure Maven 2 to use the snapshot repository for Apache. Snapshot repositories are typically configured per user at ~/.m2/settings.xml. The following example, added to your settings.xml, will add a profile for the Apache snapshot repository.

          <name>Maven Snapshots</name>
          <name>Maven Plugin Snapshots</name>

You may either specify the profile at the command-line, each time you use 'mvn', or you may configure the profile to always be active.

To use a profile at the command-line:

# mvn -Papache [options] [<goal(s)>] [<phase(s)>]

To specify the 'apache' profile to always be active:


 Building the trunks

Now, we can compile the project.

The command is simple :

mvn clean install
Issue Commands From Top

You must make sure you build the shared, installers, and daemon project modules in addition to the apacheds module to prevent problems with stale Maven SNAPSHOT jars in the snapshot repository from causing compilation errors. This can be guaranteed by performing all Maven operations above in the top directory that you checked out: the apacheds-trunk directory.

A lot of plugins will be downloaded. If you are curious, you can then look at .m2/repository to see what has been downloaded on this step.
Building should finish with these lines:

[INFO] ------------------------------------------------------------------------
[INFO] ------------------------------------------------------------------------
[INFO] Total time: 8 minutes 30 seconds
[INFO] Finished at: Mon Oct 30 23:32:41 CET 2006
[INFO] Final Memory: 18M/32M
[INFO] ------------------------------------------------------------------------

If you want to do really safe build, run the following commands in trunks:

mvn install -Dintegration

Building the installers

Building the installers is a two phase process :

cd apacheds-trunk
mvn install
cd installers/apacheds
mvn -Pserver-installer install

That's it, the jars will be find in target/images/apacheds-1.5.?SNAPSHOT<XXXXXX>-setup.jar where XXXXXX is your local system and ? is the feature release minor number for the 1.5 branch.

Starting the server without installation

The directory apacheds-trunk/installers/apacheds-noarch contains a script for Linux (apacheds.sh) and one for Windows (apacheds.bat) which can be used for starting the server without the need to install it first (as non-root-user on Linux and non-Windows-service on Windows).


cd apacheds-trunk/installers/apacheds-noarch

Integration test

To run integration tests, just use the following command :

cd apacheds-trunk
mvn -Dintegration test


Building eclipse files

To build the .project and .classpath files for eclipse, type the following commands :

cd apacheds-trunk
mvn clean install
mvn eclipse:eclipse
cd apacheds/bootstrap-partition
mvn clean install

(The last command is necessary because eclipse:eclipse purge the target directory, and we need some generated files which has been removed. This is why we do another *mvn clean installù in the boostrap-partition module
then import all the existing project which has been created.

Maven settings

Don't forget to declare a classpath variable named M2_REPO, pointing to ~/.m2/repository, otherwise many links to existing jars will be broken.
You can declare new variables in Eclipse in Windows -> Preferences... and selecting Java -> Build Path -> Classpath Variables

Eclipse hints

Add an eclipse-apacheDS.sh file in your eclipse root directory, to allow eclipse to get more memory (e.g. 750MB)
You may also declare a specific workspace when launching eclipse. I have created a workspace-apacheDS directory in my HOME directory, where all the ApacheDS project is built when I use Eclipse.

<eclipse_root>/eclipse -data $HOME/workspace-apacheDS -vm java -vmargs -Xmx750M

Launch eclipse :


Eclipse plugins

Coding standards

The coding standards including an eclipse code formatting profile is available here.

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

Unsubscribe or edit your notifications preferences