Reference:  Maven Developer Guide at JBoss.

Pre-requisites:

1) Ensure that the parent pom of the project has atleast version 5 of the JBoss Parent pom.

2) You have done the settings.xml in your local home directory under $HOME/.m2/settings.xml as described in the maven dev guide shown above.

Release Process:

1) Prepare the Release

perl -pi -e 's/1.2.0-SNAPSHOT/1.2.0.GA/g' `find . -name \*.xml -or -name \*.java`

2) Checkin the updated poms

3) mvn deploy

Ensure that you see something like this:

[INFO] Installing /home/anil/security/security-spi/branches/Branch_2_0/pom.xml to /home/anil/.m2/repository/org/jboss/security/jboss-security-spi-pom/2.0.4.SP4/jboss-security-spi-pom-2.0.4.SP4.pom
[INFO] [deploy:deploy {execution: default-deploy}]
Uploading: https://repository.jboss.org/nexus/service/local/staging/deploy/maven2//org/jboss/security/jboss-security-spi-pom/2.0.4.SP4/jboss-security-spi-pom-2.0.4.SP4.pom
1K uploaded  (jboss-security-spi-pom-2.0.4.SP4.pom)

4) Log in to Nexus with your jboss.org password.

https://repository.jboss.org/nexus/index.html

5) On the LHS, you will see, "Staging" link.  Click that.  Now in the upper window, you will "JBoss Release Staging Profile".  Click on that one.  Now in the lower window, you will see rows and your jboss.org id will be one of them.  Once you click that, the bottom window will show the archives that have been uploaded.

6) If everything is fine, right click and choose "Close"  rather than "Drop".   Provide a comment for the checkin.

7)  Now that you have closed the staging environment.   You will need to "Promote" this release to the public archives.

Post Release

8) Now in your project.

perl -pi -e 's/1.2.0.GA/1.3.0-SNAPSHOT/g' `find . -name \*.xml -or -name \*.java`

This will bump up the version number to the next release version for development.