commit | fa6a7e30262bdbbe41775afbe9039fd3f5e2f08f | [log] [tgz] |
---|---|---|
author | Saša Živkov <sasa.zivkov@sap.com> | Tue Jan 26 14:37:52 2016 +0100 |
committer | Saša Živkov <sasa.zivkov@sap.com> | Tue Jan 26 15:26:32 2016 +0100 |
tree | 0c2564a904485d9fc54c1b2a2435a1949c81f7aa | |
parent | 91ae30bd2bfaf4767d845759aad60972719c477f [diff] |
Add profile for signing artifacts Publishing artifacts to maven central requires signing. To make signing work I added the following configuration in the $HOME/.m2/settings.xml: <profiles> <profile> <id>gpg</id> <properties> <gpg.executable>gpg</gpg.executable> <gpg.passphrase></gpg.passphrase> </properties> </profile> </profiles> <activeProfiles> <activeProfile>gpg</activeProfile> </activeProfiles> as documented in [1]. Note that the executable could be named gpg or gpg2 depending on the platform. Use the following command to build, sign and stage the artifacts to the OSS Sonatype: mvn clean deploy -DperformRelease=true \ -DaltDeploymentRepository=sonatype-nexus-staging::default::https://oss.sonatype.org/service/local/staging/deploy/maven2/ [1] https://gerrit-review.googlesource.com/Documentation/dev-release-deploy-config.html Change-Id: I4faede2f754656772320c326f4890e2c74a9dce0