Skip to content

Latest commit

 

History

History
46 lines (40 loc) · 1.65 KB

Release.md

File metadata and controls

46 lines (40 loc) · 1.65 KB

Configuration for release to maven central

  • Register at sonatype jira - credential should be used in ossrh server section.
  • Create the task in sonatype's jira for getting permission to deploy (see OSSRH-44075)
  • Generate gpg key for signing artifacts. You can use steps from sonatype blog - use only steps for generating keys and registering to the central server - rest should be already configured.

Fragment from settings.xml (replace variables with values above):

  <servers>
    <server>
      <id>ossrh</id>
      <username>${ossrh.username}</username>
      <password>${ossrh.password}</password>
    </server>
  </servers>

  <profiles>
    <profile>
      <id>ossrh</id>
      <activation>
        <activeByDefault>true</activeByDefault>
      </activation>
      <properties>
        <gpg.executable>gpg</gpg.executable>
      </properties>
    </profile>
  </profiles>

Then you can simply run the command below and snapshot are going to be deployed to ossr sonatype repository.

mvn clean deploy -Prelease

Release is performed by two commands

mvn release:clean release:prepare -Prelease
mvn release:perform -Prelease

Note: The gpg agent should ask for the passphrase to your gpg key automatically, in case that does not happen you can try to add property to the <properties> section:

<gpg.passphrase>${gpg.password}</gpg.passphrase>

This approach is however not recommended, as it is not secure to store your passphrase anywhere on the filesystem.