Appendix: Release Prereqs
Apache Isis releases are built using Java 7, enforced using the maven toolchains plugin. Ensure that Java 7 is installed and the toolchains plugin is configured, as described in the contributors' guide.
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 (
secring.gpg etc), and have
gpg on your operating system PATH.
Note also that the mSysGit version of
If you use Atlassian’s SourceTree, this also bundles a version of
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
<settings> <servers> <server> <id>apache.releases.https</id> <username>xxxxxxx</username> <password>yyyyyyy</password> </server> ... </servers> ... </settings>
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>