[ http://jira.codehaus.org/browse/SCM-195?page=all ]
Brett Porter moved MRELEASE-78 to SCM-195: ------------------------------------------ Version: (was: 2.0-beta-4) 1.0-beta-3 Fix Version: (was: 2.0-beta-4) 1.0 Complexity: Intermediate Key: SCM-195 (was: MRELEASE-78) Project: Maven SCM (was: Maven 2.x Release Plugin) > Wrong SCM info put by the release plugin for modules > ---------------------------------------------------- > > Key: SCM-195 > URL: http://jira.codehaus.org/browse/SCM-195 > Project: Maven SCM > Type: Bug > Versions: 1.0-beta-3 > Environment: Sun JDK 1.5, M2 2.0.3-SNAPSHOT (2006-01-30), Subversion SCM > Reporter: Arik Kfir > Fix For: 1.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