[
http://jira.codehaus.org/browse/MRELEASE-528?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=212230#action_212230
]
John Crim edited comment on MRELEASE-528 at 3/3/10 12:48 AM:
-------------------------------------------------------------
Delete this comment.
was (Author: j...@medio):
Here's the issue I just ran in to, which seems to be related, and might be
a better illustration.
I have a project with submodules as follows:
{noformat}
/common/projectA/trunk/
./pom.xml
./module1
./module2
{noformat}
With version 2.0 of the release plugin, when I release, the tag becomes:
{noformat}
/common/projectA/tags/projectA-1.0/trunk/
./pom.xml
./module1
./module2
{noformat}
Whereas it should be:
{noformat}
/common/projectA/tags/projectA-1.0/
./pom.xml
./module1
./module2
{noformat}
It appears that the tag is being created from the wrong working dir. It's
being created from {{/common/projectA/}}, where it should be
{{/common/projectA/trunk/}}.
With version 2.0-beta-8 of the release plugin, this layout worked as expected.
> 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
