[jira] Commented: (MRELEASE-116) Wrong SCM info put by the release plugin for modules

["Emmanuel Venisse (JIRA)" <ji...@codehaus.org>]

    [ http://jira.codehaus.org/browse/MRELEASE-116?page=comments#action_65627 ] 

Emmanuel Venisse commented on MRELEASE-116:
-------------------------------------------

I moved this issue to the release plugin because I think it's related to it.

This pb must be fix in SubversionScmTranslator.
Instead of send the user tagname to SvnTagBranchUtils.resolveUrl, the tagname sended must be tagname/path_to_the current_module.

If in parent pom, scm url is like this : scm:svn:protocol://path_to_parent/
and in module : scm:svn:protocol://path_to_parent/path_to_module/
the tagname must be for the module : tagname/path_to_module

> Wrong SCM info put by the release plugin for modules
> ----------------------------------------------------
>
>          Key: MRELEASE-116
>          URL: http://jira.codehaus.org/browse/MRELEASE-116
>      Project: Maven 2.x Release Plugin
>         Type: Bug

>     Versions: 2.0-beta-4
>  Environment: Sun JDK 1.5, M2 2.0.3-SNAPSHOT (2006-01-30), Subversion SCM
>     Reporter: Arik Kfir
>      Fix For: 2.0

>
>
> Hi,
> I have a project with several modules in it. The entire project is
> stored in one SVN repository, in the following layout:
> myproject
>   |
>   +-- module A
>   |
>   +-- module B
>   |
>   +-- .....
> The root pom has a <scm> url like "http://svn.myserver/.../trunk/", and each sub module also has its own <scm> tag with a url such as "http://svn.myserver/.../trunk/moduleA", etc.
> When running "release:prepare", the URL encoded back into the modules' POMs (the back-to-trunk pom, not the released one) is the same URL as the root POM, rather than the original module's SCM url. So module A's <scm> urls would be "http://svn.myserver/.../trunk/" without the "moduleA" directory appended to it (as it was before releasing).
> Carlos has pointed out to me that the best practice for this use case is not specifying the <scm> tag for the modules' POMs at all. He did, however, also noted that it's still a bug - hence this JIRA ;-)
> Cheers.

-- 
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