[
http://jira.codehaus.org/browse/MRELEASE-261?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_127722
]
David Delbecq commented on MRELEASE-261:
----------------------------------------
Hi all,
making assumption about directory structure and the fact there is a common
ancestor is wrong too!
I have this svn structure
* http://server/project/topModule/trunk/pom.xml
* http://server/project/Module1/trunk/pom.xml
* http://server/project/Module2/trunk/pom.xml
and the developper desktop structure based on that svn:
{pre}
/home/user/dev/project/topModule (=http://server/project/topModule/trunk/)
+ pom.xml
+ Module1 (=http://server/project/Module1/trunk/)
+ pom.xml
+ Module2 (=http://server/project/Module2/trunk/)
+ pom.xml
{/pre}
I expect release plugin to read the submodules pom files, and especially the
<scm> entries in that poms, that clearly indicate the svn path of each
submodule, which should be tagged as this (using 1.1.1 as release version):
* http://server/project/topModule/tags/1.1.1/pom.xml
* http://server/project/Module1/tags/1.1.1/pom.xml
* http://server/project/Module2/tags/1.1.1/pom.xml
currently, only the first tag is generated, not the submodules tags.
The idea is that, during release, if plugin encounter a submodule which as a
<scm> which is different than that of parent, it should also tag it.
> release:prepare shouls support flat directory multimodule projects
> ------------------------------------------------------------------
>
> Key: MRELEASE-261
> URL: http://jira.codehaus.org/browse/MRELEASE-261
> Project: Maven 2.x Release Plugin
> Issue Type: Improvement
> Environment: linux / maven2 / svn
> Reporter: [EMAIL PROTECTED]
>
> What I mean by flat file structure firstly.
> parent/pom.xml
> module1/pom.xml
> module2/pom.xml
> .
> .
> .
> module15/pom.xml
> the parent references the modules like so
> <modules>
> <module>../module1</module>
> <module>../module2</module>
> .
> .
> .
> <module>../module15</module>
> </modules>
> When i release:prepare only the parent project is tagged the modules
> projects versions are incremented etc but the modules are not tagged in svn.
> I use this structure as i use eclipse as my IDE.
> I would love to see a fix for the issue marked as closed here
> http://jira.codehaus.org/browse/MRELEASE-138. I am currenrly tagging by hand
> each submodule of the projects but it would be so nice to have the release
> plugin do this for me.
> forgive my english.
--
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
