Releasing Procedure

Introduction

This page describes the procedure to follow when releasing Jukito. It is targetted to project owners and contributors.

Starting point

The starting point is the Sonatype OSS Maven Repository User Guide. Follow all the steps in there. Among other things you will have to install GPG and generate keys. The process is explained in this guide.

Specifying your Google Code credentials

The various deployment steps need Maven to know your Google Code credentials. You specify them on your local machine by adding the following to Maven's settings.xml:

<servers>
  ...
  <server>
    <id>github.com</id>
    <username>philippe.beaudoin</username>
    <password>0123456789ABCD</password>
  </server>
  ...
</servers>

Deploying a snapshot

Important! Make sure you quit Eclipse before doing that, so that there is no interference between Eclipse automatic building and Maven.

This is explained in section 7a.2 of the previous document.

It's accomplished simply via:

mvn clean deploy

To see the snapshot, go to Sonatype's Nexus at http://oss.sonatype.org/ and navigate to Repositories > Snapshots > org > jukito.

Releasing a new version

Important! Make sure you quit Eclipse before doing that, so that there is no interference between Eclipse automatic building and Maven.

Releasing is done in two steps: first staging a release, the performing the actual release.

Staging the release

This is explained in section 7a.2 of the previous document.

Before you deploy a release you should make sure all the source is committed and pushed to the Google Code repository. You do not have to tag the code, it will be done automatically by Maven in the following steps. This is done via:

mvn release:clean
mvn release:prepare -Dgpg.passphrase=yourpassphrase

Answer all the questions. The artifacts will be signed so you have to enter your GPG passphrase. Following that, Maven will automatically modify the POM and commit, tag and push the code a couple of times. If things go wrong at that point, you should hg strip any automatic commits by Maven (if they have not yet been pushed) and start back at release:clean.

The next step is performing staging the actual release through the following command:

mvn release:perform -Dgpg.passphrase=yourpassphrase

To see the staging release, go to Sonatype's Nexus at http://oss.sonatype.org/ and navigate to Staging Repositories. You must be logged in to see this.

Releasing

This is explained in section 8 of the previous document.

Once you see the staging release on Nexus, simply select it, click Close, and enter a brief description.

Next, the artifacts should be downloaded and tested.

When everything works, click the Release button.

To see the release, go to Sonatype's Nexus at http://oss.sonatype.org/ and navigate to Repositories > Releases > org > jukito.