Archiva release process

  1. Post to the dev list a few days before you plan to do an Archiva release
  2. Recreate the staging repository on - make sure that it is not scanned (so that .index* is not created). Your maven setting must contains the entry to be able to deploy.
  3. If there are changes in the parent pom, release parent pom –
    • mvn release:prepare (verify that it has been properly tagged)
    • mvn release:perform (verify that it has been deployed correctly in the staging repo)
  4. Update the parent pom version of archiva –
    • change the parent pom version to the archiva-parent version that has just been released
    • commit the changes made
  5. Update the release notes and the site.xml for version changes in archiva-docs
  6. Verify that the webapp-tests are building successfully. Since it is in a separate profile but inside the Archiva source tree, it will not be released but will still be included in the release tag. If some tests are failing, comment it out first so that only the passing tests are executed when the webapp-tests module are built from the tag.
  7. Release archiva You should have a GPG agent running (preferred), and confirm it works by running "gpg -ab" (type some text and press Ctrl-D). If you do not have a GPG agent running, make sure that you have the "apache-release" profile set in your settings.xml as shown below.

    Set your user credentials for the stage repo in the servers section of your settings.xml for archiva-repository.releases.

    Execute mvn release:prepare (check that it has been properly tagged. the tag name must be.. archiva-[VERSION]).

    Next, execute mvn release:perform

    Download the uploaded files via wget:

    Verify the signatures:
    gpg -v

    The documentation is deployed as part of the process to the final location for review in the vote: If the vote doesn't pass, the documentation will need to be removed from the server for redeployment. Commit the sources and binaries from org/apache/archiva/archiva-jetty, and org/apache/archiva/archiva to the svn distribution tree. First in dev tree: (if the vote pass they will be copied to release tree)

    svn co archiva-dev-release
    cd archiva-dev-release

    Call for a vote in the dev list and wait for 72 hrs. for the vote results. 3 binding votes are necessary for the release to be finalized. example If the vote fails or needs to be canceled, the version number should not be re-used if the version was made available for public download. After the vote has passed, move the files from dist dev to dist release: svn mv to To sync the jars to ibiblio, execute:

    NOTE: the stage plugin doesn't work with maven3 you must use maven 2.2.1

      mvn stage:copy -Dsource=""
         -Dversion=1.3 -DrepositoryId=apache.releases

    mark the appropriate release version in JIRA as complete Update the archiva site ( for the versions and release notes URL and run mvn site-deploy. The 3 properties to change are at the bottom of pom.xml before generating the site. Once mirroring done (can be 24H): remove previous versions from

    Publish the reference docs (sh ./ in the archiva-modules directory) from the release tag. You may have to exclude the archiva-webapp module to do this, and will require MAVEN_OPTS=-Xmx256m. You may need to use Maven 2.2.1 instead of Maven 3.x for this.

    Send out an announcement of the release to: