[
http://jira.codehaus.org/browse/MRELEASE-528?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=211516#action_211516
]
Alexandre Navarro commented on MRELEASE-528:
--------------------------------------------
Instead to have
tags/module1-${version}/${inside(trunk/project1/module1)}
you will have
tags/module1-${version}/project1/module1/${inside(trunk/project1/module1)}.
So in your case, tags/module1-${version}/project1/module2/pom.xml will not
exist even though
trunk/project1/module2/pom.xml exists and you released in
trunk/project1/module1.
If you release is directly in trunk, you will have the 2 modules.
The issue with tags/module1-${version} is the compare with some svn client will
not work.
For instance, in eclipse, if you try Team -> Compare with tags (I don't
remember if it is with subeclipe or subversive), it will not work with
tags/module1-${version}/${inside(trunk/project1/module1)} but work only with
tags/module1-${version}/project1/module1/${inside(trunk/project1/module1)}.
Nevertheless, it is possible to compare with by url to resolve the problem.
When you migrate from cvs to svn (with cvs2svn), if a tag was made on HEAD in
the directory project1/module1, the result after migration will be
tags/module1-${version}/project1/module1/${inside(trunk/project1/module1)}. It
confirms this standard naming convention in svn. It is not very known (I
discovered it in Eclipse recently).
I think the only change on your code is to replace the default tagBase
tags/module1-${version} by tags/module1-${version} + directories after trunk in
the scm url.
I hope I'm clear. Tell me if it is not the case.
> The directory layout of Release plugin does not respect the standard layout
> of svn scm.
> ---------------------------------------------------------------------------------------
>
> Key: MRELEASE-528
> URL: http://jira.codehaus.org/browse/MRELEASE-528
> Project: Maven 2.x Release Plugin
> Issue Type: Bug
> Components: prepare
> Affects Versions: 2.0
> Reporter: Alexandre Navarro
>
> The directory layout of Release plugin does not respect the standard layout
> of svn scm.
> For instance, if you have repo like
> trunk/project1/module1/pom.xml (where you want to launch mvn release)
> the tags will be in
> tags/module1-${version}/pom.xml
> but the standard is
> tags/module1-${version}/project1/module1/pom.xml
> See for example how in eclipse the compare with tags works (not by url).
> You can customize the tagBase to have this but it should be by default.
> Thanks in advance
--
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
