[MRELEASE-582] Regression: releasing an individual module on a separate release cycle tags the entire project instead

• Type: Bug
• Status: Closed
• Priority: Critical
• Resolution: Not A Problem
• Affects Version/s: 2.0-beta-9, 2.0
• Component/s: prepare
• Assignee: Brett Porter
• Reporter: Carlo de Wolf
• Created: 29/Jul/10 04:43
• Updated: 02/Oct/10 08:54
• Resolved: 02/Oct/10 08:54

Description

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

Issue Links

• relates to: MRELEASE-546 regression introduced in MRELEASE-261
• relates to: MRELEASE-261 release:prepare should support flat directory multi-module projects