We need you!


The IzPack documentation needs work, and you are invited to edit it!

Versions Compared


  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: Migrated to Confluence 5.3

Deploying IzPack Versions to Public Repositories

General Requirements

  • You must be an IzPack developer at Codehaus.
  • You need a GnuPG public key.
  • You need to import the Codehaus CA certificates to your local JDK

Create and Export a GnuPG Key

Your public key must be added to the KEYS file in the source code parent directory:

No Format
gpg --list-sigs "your real name" >> KEYS
gpg --armor --export "your real name" >> KEYS

Export your public key to a public key server:

Code Block
gpg --keyserver search.keyserver.net --send-key <your_key_id>

Without your GPG key exported to a public key server you won't be able to close a Codehaus Nexus staging repository and thus activating new releases. 

In case of trouble exporting from the command line you could try submitting your key via the web UI of a keyserver of your choice, for example: http://pool.sks-keyservers.net:1137

For more information on how to create and distribute GPG keys, look at the GNU Privacy Handbook.

Configure Codehaus Maven credentials

The Codehaus parent, which relies the IzPack parent POM on, requires authentication usign the following convention in your $M2_HOME/settings.xml:

Code Block
titleExample of settings.xml
        <id>codehaus.org</id> <!-- used for site deployment -->
        <id>codehaus-nexus-staging</id> <!-- used for release deployment -->
        <id>codehaus-nexus-snapshots</id> <!-- used for snapshot deployment -->

The server IDs are given by the Codehaus parent POM, use your Codehaus account as username and password. For encoding your personal password see the Maven documentation.

For further information see also: Codehaus Maven Repository Usage Guide.

Install the Codehaus CA Certificate into the Java JDK

  1. Download the StartSSL CA and StartSSL Intermediate CA to your local filesystem.
  2. Install the downloaded certificate into the JDK
If do not have permission to modify your JDK installation you can add the certificate to your own keystore in your home directory:
Code Block
titleExample script for installing the Codehaus CA into the JDK
export JAVA_HOME=/usr/java/jdk1.6.0_37
pushd $(dirname $0)
$JAVA_HOME/bin/keytool -import -alias StartSSL-CA -file startssl-CA.pem -keystore $KEYSTORE
$JAVA_HOME/bin/keytool -import -alias StartSSL-Intermediate -file startssl-Intermediate.pem -keystore $KEYSTORE

In case of using your own keystore, you must tell Maven to use it by exporting special Maven options:

Code Block
titleExample of how to prepare the Maven call with an own JDK keystore
export MAVEN_OPTS="-Djavax.net.ssl.keyStore=$HOME/.keystore \
    -Djavax.net.ssl.keyStorePassword=<your_keystore_pwd> \
    -Djavax.net.ssl.trustStore=$HOME/.keystore \

For more information, see Installing a new CA into the JDK.

Deploying IzPack Snapshots

Any IzPack developer is encouraged to publish new -SNAPSHOT versions as they publish changes to the Codehaus Git repository. Public snapshot deployments can be done each time by a developer provided the code passes automatic tests (do not skip tests before deploying).

Test your snapshot locally by deploying it to the local repository:

Code Block
mvn clean install

Deploying a snapshot to the wild is done by:

No Format
mvn clean verify deploy

Deploying IzPack Releases

Note: Before releasing, ask the fellow developers whether they agree!

For a comprehensive manual how to manage Codehaus deployments see Performing a Release. 

As an example, we will consider the release of version 5.2.0.

Do a dry run

No Format
mvn release:prepare [--batch-mode] -DdryRun=true \
                    -DdevelopmentVersion=5.2.1-SNAPSHOT \
                    -DreleaseVersion=5.2.0 \
                    -DpreparationGoals='clean verify install' \


Build locally and prepare the staging repository at Codehaus Nexus:

No Format
mvn release:clean

mvn release:prepare [--batch-mode] \
                    -DdevelopmentVersion=5.2.1-SNAPSHOT \
                    -DreleaseVersion=5.2.0 \
                    -DpreparationGoals='clean verify install' \

mvn release:perform -Dusername=your_codehaus_login

Don't forget to push the local POM changes and tags to Github after releasing: 

Code Block
git push --tags

Close, promote and release from the staging repository at Codehaus Nexus:

Log in at Codehaus Nexus Staging Repositories, check the staging repository and if everything is fine, Close and Release it (in this order).


  • You won't be able to perform release:prepare without having the HTTP credentials set in settings.xml, to be able to upload files to the staging storage at Codehaus Nexus
  • You won't be able to close a Nexus staging repository without having your GPG key exported to a key server.
  • Things work better if your local account name matches the one at Codehaus, and you don't have to specify the username parameter. Otherwise, things may break, especially the Git pushes.

Recovering from Failed Releases

There are several states you may get in after the release process described above fails:

Recover the staging repository:

Log in at  Codehaus Nexus Staging Repositories, select the the staging repository entry which failed and drop it.

Reset the local git repository to the state before releasing:

First remove the additional files generated by the release plugin:

Code Block
mvn release:clean

Using git log get  the latest commit before the auto-generated commit of the release plugin follow, for example:

Code Block
commit 49a769a0eefa7476d5ccc3849692ffe7b6e5ed2e
Merge: d682c30 3218c81
Author: René Krell <renda.krell@gmail.com>
Date: Tue Oct 15 09:45:05 2013 -0700
Merge pull request #143 from rkrell/IZPACK-993

[IZPACK-993] Dynamic variables - add configuration attribute to control whether to escape backslashes when reading from option and INI files

Now you can reset the local repository to the original state (or using FETCH_HEAD if the remote repository is still blocked and unchanged).

Code Block
reset --hard  49a769a0eefa7476d5ccc3849692ffe7b6e5ed2e

Check whether the release plugin has already tagged the target version using git tag. If yes, delete the tag to avoid release:perform from failing:

Code Block
git tag --delete izpack-5.0.0-rc1

Now you can repeat the release process from the beginning.


Post-processing and Announcing Releases

  1. Use WebDAV at https://dav.codehaus.org/dist/izpack/ to push releases from the Maven repository
    Example 5.0.0-rc1:
    Copy izpack/izpack-dist/target/izpack-dist-5.0.0-rc1.jar  to  webdavs://dav.codehaus.org/dist/izpack/releases/5.0.0-rc1/izpack-dist-5.0.0-rc1-installer.jar
  2. Use the following channels for announcements:
    Website izpack.org: https://github.com/izpack/izpack.github.com, automatically deployed to http://izpack.org
    Blog news.izpack.org: Register and post an announcement. This is automatically forwarded to Twitter and Facebook.
    Mailing list: user@izpack.codehaus.organnounce@izpack.codehaus.org
    Google+ group IzPack (in case you're a maintainer): https://plus.google.com/105618715093492300071/posts
    Facebook: http://www.facebook.com/izpack
    IzPack.org website: https://github.com/izpack/izpack.github.com, automatically deployed to http://izpack.org
    Twitter (ping @jponge): @izpack 

Update the Codehaus GIT repository

After deploying a snapshot or release push all differences from GitHub to Codehaus to have it in sync:

Code Block
#git remote add codehaus ssh://git@git.codehaus.org/izpack.git
git push codehaus master
git push --tags codehaus master