Regression: releasing an individual module on a separate release cycle tags the
entire project instead
------------------------------------------------------------------------------------------------------
Key: MRELEASE-582
URL: http://jira.codehaus.org/browse/MRELEASE-582
Project: Maven 2.x Release Plugin
Issue Type: Bug
Components: prepare
Affects Versions: 2.0, 2.0-beta-9
Reporter: Carlo de Wolf
Priority: Critical
Attachments: dummy.tgz
We have a lot of projects which use individual release cycles for their
respective modules. With the introduction of release plugin 2.0-beta-9 it
doesn't tag the module anymore, but the whole project, thus breaking this
previous working setup.
See for example: http://anonsvn.jboss.org/repos/jbossas/projects/jboss-aspects/
And a broken tag:
http://anonsvn.jboss.org/repos/jbossas/projects/jboss-aspects/tags/jboss-aspects-build-1.0.2/
To recreate the bug:
$ svn admin create $HOME/tmp/svn-repo
$ svn mkdir --parents file:///$HOME/tmp/svn-repo/dummy/tags
file:///$HOME/tmp/svn-repo/dummy/trunk
$ svn co file:///$HOME/tmp/svn-repo/dummy/trunk dummy
$ (cd dummy; tar zxvf ../dummy.tgz)
Modify build/pom.xml to substitute $HOME and use a broken version of release
plugin.
$ svn add .
$ svn commit
$ mvn release:prepare
$ svn ls file:///$HOME/dummy/tags/dummy/tags/build-1.0.x
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
