[ http://jira.codehaus.org/browse/SCM-195?page=comments#action_65626 ]
Emmanuel Venisse commented on SCM-195:
--
I just tested this pb with a little project with these scm urls :
root : scm:svn:file:///D:/testSCM-195-repos/trunk/
moduleA: scm:svn:file:///
[ http://jira.codehaus.org/browse/SCM-195?page=comments#action_65362 ]
Brett Porter commented on SCM-195:
--
we probably need to specify trunk base as well as tag base
> Wrong SCM info put by the release plugin for modules
> --
[ http://jira.codehaus.org/browse/SCM-195?page=comments#action_65273 ]
Arik Kfir commented on SCM-195:
---
emmanuel: when the release plugin writes the modified pom back into svn (with
the released version, etc), it also writes a wrong scm url (under the
tag).
[ http://jira.codehaus.org/browse/SCM-195?page=comments#action_65272 ]
Emmanuel Venisse commented on SCM-195:
--
Sorry, but I don't understand what is the problem.
> Wrong SCM info put by the release plugin for modules
> --
[ http://jira.codehaus.org/browse/SCM-195?page=comments#action_64646 ]
Brett Porter commented on SCM-195:
--
I tracked this down to SvnTagScmUtils.resolveTagUrl - anything with moduleA on
the end comes back with moduleA appended
> Wrong SCM info put by the r
