Skip to content
krmorse edited this page Jan 21, 2016 · 5 revisions

Releasing to Maven central

One-time Setup

  • Install Maven 3
  • Install gpg to sign the artifacts
brew install gpg
  • Get a copy of the the gpg key pair archive from Matt Cholick, Kyle Morse, or Charles Ferentchak
  • Place the contents of the key pair archive in ~/.gnupg
  • Add login information to Sonatype's repository to your ~/.m2/settings.xml (again getting the credentials from Matt, Kyle, or Charles)
<settings>
    <servers>
        <server>
            <id>sonatype-nexus-snapshots</id>
            <username>user</username>
            <password>password</password>
        </server>
        <server>
            <id>sonatype-nexus-staging</id>
            <username>user</username>
            <password>password</password>
        </server>
    </servers>
</settings>

Releasing to Sonatype OSS (central)

This is a stripped down version of a much, much longer guide https://docs.sonatype.org/display/Repository/Sonatype+OSS+Maven+Repository+Usage+Guide

  • Prepare the release (create tag & update pom)

(Make sure you have ssh keys set up for your git repo so mvn can auto push as part of this process)

mvn release:clean
mvn release:prepare
  • Release!
mvn release:perform
  • Log in to https://oss.sonatype.org/index.html (same credentials as settings.xml)
  • Select the closed staging repository for com.rallydev (the release step generated this)
  • Click release
    • The guide has step-by-step instructions and screenshots for releasing the staged repository in step 8a. The first half of step 8a, closing the staging directory, was already done by the nexus-staging-maven-plugin
  • Finally, draft a Github release from the tag created by Maven.
Clone this wiki locally