Publishing builds to Maven
--------------------------
1. You must have gpg set up and your key registered, as described at <hhttp://blog.sonatype.com/people/2010/01/how-to-generate-pgp-signatures-with-maven/>
2. You must provide a property `gpg.passphrase` in your `settings.xml` in the `release` profile e.g.
<profile>
<id>release</id>
<properties>
<gpg.passphrase>myPassPhrase</gpg.passphrase>
</properties>
</profile>
3. You must have a JBoss Nexus account, configured with the server id in `settings.xml` with the id `jboss-releases-repository` e.g.
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
Pete Muir or Rafael Benevides : Do you know what to do to fix this section in the CONTRIBUTING.md?
Publishing builds to Maven
--------------------------
1. You must have gpg set up and your key registered, as described at <hhttp://blog.sonatype.com/people/2010/01/how-to-generate-pgp-signatures-with-maven/>
2. You must provide a property `gpg.passphrase` in your `settings.xml` in the `release` profile e.g.
<profile>
<id>release</id>
<properties>
<gpg.passphrase>myPassPhrase</gpg.passphrase>
</properties>
</profile>
3. You must have a JBoss Nexus account, configured with the server id in `settings.xml` with the id `jboss-releases-repository` e.g.
<server>
<id>jboss-releases-repository</id>
<username>myUserName</username>
<password>myPassword</password>
</server>
4. Add `org.sonatype.plugins` plugin group to your `settings.xml` so nexus plugin can be available for publishing scripts.
<pluginGroups>
<pluginGroup>org.sonatype.plugins</pluginGroup>
</pluginGroups>