Controls
Built with Seam
You can find the full source code for this website in the Seam package in the directory /examples/wiki. It is licensed under the LGPL.
| Comparing current revision with historical revision 2. |
From line 0 changed to line 0:
The |org.jboss.weld:weld-parent| module sits at the top of the hierarchy for every POM in Weld and the CDI TCK. It controls the plugin versions used, as well as specifying the distribution management. It is located [here=>https://svn.jboss.org/repos/weld/build/trunk/parent/]
The |org.jboss.weld:weld-parent| module sits at the top of the hierarchy for every POM in Weld and the CDI TCK. It controls the plugin versions used, as well as specifying the distribution management. It is located in the [parent=>http://github.com/weld/parent] directory of the Weld build repository.
From line 12 changed to line 12:
Make sure all the changes are checked in using |svn status|.
Make sure all the changes are checked in using:
From line 14 changed to line 14:
Now, run |mvn release:prepare --batch-mode -Drelease -DdevelopmentVersion=A-SNAPSHOT -DreleaseVersion=X -Dtag=weld-parent-X -DdryRun| - this will run through the release process, but not actually perform the tagging.
`git status`
From line 16 changed to line 16:
If the build fails, go back and correct the problems
Make sure that you have no outstanding changes, and all your changes are pushed to the remote repo.
From line 18 added to lines 18 to 25:
Let X be the current version (minus the |-SNAPSHOT|) part and Y be the next version. Run:
`mvn release:prepare --batch-mode -Drelease -DdevelopmentVersion=Y-SNAPSHOT -DreleaseVersion=X -Dtag=X -DdryRun`
This will run through the release process, but not actually perform the tagging (as indicated by the |-DdryRun| flag).
If the build fails, go back and correct the problems ;)
`mvn release:prepare --batch-mode -Drelease -DdevelopmentVersion=Y-SNAPSHOT -DreleaseVersion=X -Dtag=X -DdryRun`
This will run through the release process, but not actually perform the tagging (as indicated by the |-DdryRun| flag).
If the build fails, go back and correct the problems ;)
From line 20 changed to line 28:
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-SNAPSHOT -DreleaseVersion=X -Dtag=weld-parent-X -Dresume=false|.
Now we are ready to tag the release. Make sure the tag doesn't already exist, and run:
From line 22 changed to line 30:
+++ Perform the release to maven
`mvn release:prepare --batch-mode -Drelease -DdevelopmentVersion=Y-SNAPSHOT -DreleaseVersion=X -Dtag=X -Dresume=false`
From line 24 changed to lines 32 to 38:
Now, run |mvn release:perform nexus:staging-close -Drelease|. You should see all the artifacts uploaded to the staging repository.
+++ Perform the release to Nexus
Now, run:
`mvn release:perform nexus:staging-close -Drelease`
You should see all the artifacts uploaded to the staging repository. You can promote them through the web interface.
Now, run:
`mvn release:perform nexus:staging-close -Drelease`
You should see all the artifacts uploaded to the staging repository. You can promote them through the web interface.
