Appendix: Release Prereqs
This section (appendix) describes the prerequisites for the release process.
Public/private key
The most important configuration you require is to set up public/private key pair.
This is used by the maven-release-plugin
to sign the code artifacts.
See the page on key generation for more details.
In order to prepare the release, you’ll (need to) have a ~/.gnupg
directory with the relevant files (gpg.conf
, pubring.gpg
, secring.gpg
etc), and have gpg
on your operating system PATH.
If on Windows, the equivalent directory is Note also that the mSysGit version of If you use Atlassian’s SourceTree, this also bundles a version of |
Maven settings.xml
During the release process the maven-deploy-plugin
uploads the generated artifacts to a staging repo on the Apache repository manager.
This requires your Apache LDAP credentials to be specified in your ~/.m2/settings.xml
file:
<settings>
<servers>
<server>
<id>apache.releases.https</id>
<username>xxxxxxx</username>
<password>yyyyyyy</password>
</server>
...
</servers>
...
</settings>
where xxxxxxx
and yyyyyyy
are your Apache LDAP username and password.
For more information, see these ASF docs.
It is also possible to configure to use |
Also, set up keyphrase for gpg
; this avoids being prompted during release:
<profiles>
<profile>
<id>gpg</id>
<properties>
<gpg.executable>gpg2</gpg.executable>
<gpg.passphrase>this is not really my passphrase</gpg.passphrase>
</properties>
</profile>
...
</profiles>
<activeProfiles>
<activeProfile>gpg</activeProfile>
...
</activeProfiles>