Prerequisites:
1) Remove any vestigal references to org.apache.maven.plugins maven-pluto-plugin. This was caused by an incorrect <groupId> that appeared a while back in the Pluto POM. Once you remove these references, they shouldn't come back:
<pluginGroups> <pluginGroup>org.apache.pluto</pluginGroup> </pluginGroups> |
The Maven 2 release plugin is used to create the tag. The Maven 2 assembly plugin is used to create the binary and source distributions.
TODO: fix paths
With Maven 2, creating the tag and creating the distributions occur at the same time. When the release
plugin is run, be sure to activate the assembly
profile (using -Passembly,build-assemblies
on the command line). When the assembly
and build-assemblies
profiles are activated, the distributions will be generated in assembly/target/assembly/out
.
The release plugin will (not in this exact order, but close):
1.1.0-SNAPSHOT
, you are releasing 1.1.0
).1.1.0
then the next version is probably 1.1.1-SNAPSHOT
).assembly
profile is activated)mvn deploy
and mvn site-deploy
svn up svn st |
2. Run mvn -Passembly,build-assemblies release:prepare
3. Run mvn -Passembly release:perform
You should see your new tag appear under tags. You should see a commit that look something like:
esm@clue:~$ svn log https://svn.apache.org/repos/asf/portals/pluto/tags --limit 1 ------------------------------------------------------------------------ r506076 | esm | 2007-02-11 12:29:23 -0500 (Sun, 11 Feb 2007) | 1 line [maven-scm] copy for tag pluto-1.1.0 ------------------------------------------------------------------------ |
4. Binaries will be in assembly/target/assembly/out