Deploying IzPack Versions to Public Repositories
- 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:
Export your public key to a public key server:
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:
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
- Download the StartSSL CA and StartSSL Intermediate CA to your local filesystem.
- Install the downloaded certificate into the JDK
In case of using your own keystore, you must tell Maven to use it by exporting special Maven options:
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:
Deploying a snapshot to the wild is done by:
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.
For your own security, using
--batch-mode is not really recommended since you have to enter your GPG passphrase in clear text on the command line, which could be saved for example in .bash_history. Rather wait and enter this passphrase as soon as Maven requests it on the command line input.
As an example, we will consider the release of version 5.0.0-rc2.
Do a dry run
Build locally and prepare the staging repository at Codehaus Nexus:
Don't forget to push the local POM changes and tags to Github after releasing:
and to Codehaus (provided a remote codehaus initialized to ssh://email@example.com/izpack.git):
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:
git log get the latest commit before the auto-generated commit of the release plugin follow, for example:
Now you can reset the local repository to the original state (or using FETCH_HEAD if the remote repository is still blocked and unchanged).
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:
Now you can repeat the release process from the beginning.
Post-processing and Announcing Releases
- Use WebDAV at https://dav.codehaus.org/dist/izpack/ to push releases from the Maven repository
- 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: firstname.lastname@example.org, email@example.com
Google+ group IzPack (in case you're a maintainer): https://plus.google.com/105618715093492300071/posts
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: