How to Release


Once you've done your first release, you'd most probably be more comfortable with the quick guide to get the release out (nevertheless, all steps are explained below):

  1. Prepare the release

    mvn clean install apache-rat:rat -Papache-release               # generates artifacts, checks for AL headers
    mvn release:prepare -DdryRun=true -DautoVersionSubmodules=true  # review pom.xml, confirm only appropiate sections have been changed
    mvn deploy -Papache-release                                     # deploy a snapshot
    mvn release:clean                                               # prepare the release 1/3
    mvn release:prepare -DautoVersionSubmodules=true                # prepare the release 2/3
    mvn release:perform                                             # prepare the release 3/3
  2. Close the staging repo

  3. Svn copy binaries and source to

  4. Run the vote and, if successful, continue with the items on the list

  5. Publish Nexus repository

  6. Publish binaries and source to the mirrors

  7. Publish latest javadocs

  8. Wait for 24 hours, then announce the release

  9. Add the next release version to JIRA

First time release managers

  1. Generate PGP code signing keys

  2. Add the PGP code signing keys to the KEYS file as documented on the Infrastructure site

  3. Put in a Infrastructure JIRA asking to get added to the jspwiki unix group on

  4. Copy the modified KEYS file to the release folder /www/ on and ensure it has 0664 permissions.

  5. Add the following servers to your Maven settings.xml file:


Note that your password doesn't need to be inside the settings.xml file, due to Maven encryption capabilities. It is also convenient to setup the ssh keys on, otherwise you'll have to enter your login password a number of times.

Create a release candidate

Generate release candidate artifacts

  1. Generate artifacts

    mvn clean install apache-rat:rat -Papache-release

    This will check that all files have AL headers and also build artifacts, sources and sign

  2. Check POMs for release

    mvn release:prepare -DdryRun=true -DautoVersionSubmodules=true 

    Perform quick diffs between pom.xml files and their sibling pom.xml.tag files to see if the license or any other info has been removed (should never happen, but just to stay on the safe side).

Prepare the release

  1. Publish a snapshot

    mvn deploy -Papache-release
  2. Prepare the release

    mvn release:clean
    mvn release:prepare -DautoVersionSubmodules=true 
  3. Stage the release for a vote

    mvn release:perform
  4. Close the staging repository

    1. Login to and select Staging Repositories on the left under Build Promotion.

    2. Select org.apache.jspwiki from the list of repositories, then click Close using "Apache JSPWiki X.Y.Z" as the description to allow others to see the repository.

  5. **Svn copy binaries and source to**, suggested structure


Run a vote

  1. Send the following to
    Subject: [VOTE] Release JSPWiki version X.Y.Z
    This is a release vote for Apache JSPWiki, version X.Y.Z. The vote will be open for at least 72 hours from now.
    It fixes the following issues:<REPLACE>
    Note that we are voting upon the source (tag), binaries are provided for convenience.
    Everybody is encouraged to vote.
    Source and binary files:<REPLACE>/jspwiki-X.Y.Z-candidate-$RC
    Nexus staging repo:
    The tag to be voted upon:
    JSPWiki's KEYS file containing PGP keys we use to sign the release:
    *** Please download, test and vote:
    [ ] +1 Approve the release
    [ ]  0 Don't mind
    [ ] -1 Disapprove the release (please provide specific comments)

Note that the PMC needs to vote upon the release before any release can be made official.

Roll Out

If the vote passes, roll out the release:

  1. Publish Nexus repository

    1. Login to and select Staging Repositories on the left under Build Promotion.

    2. Select the repository that was closed earlier, and click Release, using the description "Apache JSPWiki X.Y.Z"

  2. Publish src and bin distributions to the mirrors

    1. svn checkout

    2. svn copy the release artifacts from$VERSION-CANDIDATE to$VERSION

    3. svn delete older releases

  3. Publish javadocs on

    1. svn checkout

    2. svn add javadocs directory/ies, which have been generated as part of the release (check for */target/apidocs folders)

    3. modify the three links on so they point to the new javadocs

  4. Wait 24 hours for mirrors to sync

  5. Post link to the full release notes along with links to the major JIRA changes on the front page of the site

Announce the release

  1. Send the following from an address to,,
    Subject: [ANNOUNCE] Apache JSPWiki X.Y.Z released
    The Apache JSPWiki team is pleased to announce the release of JSPWiki X.Y.Z.
    This is the <REPLACE> release on the X.Y series of Apache JSPWiki, a feature-rich and 
    extensible WikiWiki engine built around the standard JEE components.
    The release is available here:
    JSPWiki Maven artifacts are available under org.apache.jspwiki groupId, 
    version X.Y.Z
    The full change log is available here:<REPLACE>
    A curated change log is also available here:<REPLACE>
    We welcome your help and feedback. For more information on how to
    report problems, and to get involved visit the project website at
    The Apache JSPWiki Team

Add the next release version to JIRA

  1. Add the next version number to JIRA

  2. Mark the released version as "released" with a release date


  1. Cygwin mixes Windows path with cygdrive, so mvn release:prepare fails on svn commit

    Current workaround: perform release vía cmd.exe

  2. Avoid gpg signing prompt when using Maven release plugin


  3. mvn release:prepare doesn't find svn credentials

    On your settings.xml file you should have one <server /> entry for each of the following ones:

    • apache.snapshots.https: to be able to deploy snapshots
    • apache.releases.https: to be able to deploy releases
    • to be able to create tags

    Alternatively, for the last one, you could pass -Dusername=[username] -Dpassword=[password] to the mvn command (source:

  4. Release fails after a tag has been generated and the pom versions have been incremented

    No need of mvn release:rollback, instead check out the tag and release:perform -DconnectionUrl=scm:svn:

Other links of interest