Child pages
  • How to release
Skip to end of metadata
Go to start of metadata

Prerequisites

Before releasing, please make sure that you have:

  1. Gpg key, which will be used to sign artifacts. You can find instructions here how to do it.
  2. Credentials in your maven's settings.xml file for release repository e.g.   
             <server>
              <id>sonatype-nexus-snapshots</id>
              <username>username</username>
              <password>password</password>
            </server>
            <server>
              <id>sonatype-nexus-staging</id>
              <username>username</username>
              <password>password</password>
            </server>
  3. Gpg profile in your maven's settings.xml file, which contains password for key used to signing artifacts e.g.
          <profile>
              <id>release-sign-artifacts</id>
            <activation>
                <property>
                    <name>performRelease</name>
                    <value>true</value>
                </property>
            </activation>
              <properties>
            <gpg.passphrase>password</gpg.passphrase>
              </properties>
         </profile>

Release

To perform release follow steps:

  1. Create separate branch in git, dedicated to this release version, if it is not already created.
  2. Make sure that version in pom.xml is correct for the release.
  3. Make sure project does not depend on any *-SNAPSHOT artifacts.
  4. Perform release: mvn -DperformRelease=true deploy

A this point all artifacts should be signed and deployed to OSS staging repository. Make sure that all artifacts are in place and work as expected e.g. by running integration tests. If everything works correctly, close the staging repository and release artifacts on OSS Nexus. Instructions how to do that are here. All artifacts should appear in Maven Central repository after a while (< 1h). After artifacts have been published to Maven Central repository they can not be modified.

  • No labels