Weld API and SPI Releases

This document describes the release process for the Weld APIs and SPIs. We assume you are in the root directory of the APIs. Before you start, take a look at the getting started guide.

Ensure all dependencies are released

Maven is strict (which is no bad thing!) about ensuring that all dependencies are non-snapshot before starting the release. So, check the properties in pom.xml, and release any dependencies needed.

Checking whether you are good to go

The maven release plugin is very powerful, and will transform all your POMs to a release version, tag them, and then revert trunk or the branch back to a development version. We can also do a dry run to check there are no snapshot dependencies (for example, a developer might have mistakenly put the version in a sub-module). If there are any problems, you need to fix them, and check in the changes.

Make sure all the changes are checked in using git status and verify you have merged in all branches.

Now, run mvn release:prepare --batch-mode -Drelease -DdevelopmentVersion=A.B-SNAPSHOT -DreleaseVersion=X.Y.Q -Dtag=X.Y.Q -DdryRun - this will run through the release process, but not actually perform the tagging.

If the build fails, go back and correct the problems

Tagging the release

Now we are ready to tag the release. Make sure the tag doesn't already exist, and run mvn release:prepare --batch-mode -Drelease -DdevelopmentVersion=A.B-SNAPSHOT -DreleaseVersion=X.Y.Q -Dtag=X.Y.Q -Dresume=false.

Once this finishes, verify that the tag is correct (e.g. use a browser).

Perform the release to maven

Now, run mvn release:perform nexus:staging-close -Drelease. You should see all the artifacts uploaded to the staging repository.

Upload the xsd to jboss.org

Uploading is done using SCP, SFTP, or RSYNC in a restricted secure shell on the filemgmt.jboss.org machine:

scp weld/src/main/resources/beans_1_1.xsd weld@filemgmt.jboss.org:schema_htdocs/weld