I'm guessing that when you do the release of the child module, a snapshot-version of the parent is actually being used as that's what your child pom specifies. The snapshot-version is in your local repo (or a remote repo) and still has all the properties in the scm url (it's just the released version in your corp repo that has the properties substituted). Thus, the effective-pom will have a scm url with the properties and when substituting those with the child's values, the scm url is created correctly (for the child project).
If this is the case, I would say that it is a kind of bug in the release plugin as the resulting effective-pom (based on the release version parent pom and the release version child pom) is not what was used when doing the release. As you can tell from you're case there are some differences. In your example it's for instance not possible to retrieve the code base based on the scm url of the release child project (the scm url inherited from the release version parent pom). Regarding the proprties substitution in the parent pom people normally complain that the properties are NOT substituted. And now you're complaining they are...:-) /Anders On Thu, Dec 3, 2009 at 07:27, nodje <nodje...@gmail.com> wrote: > > Hi, > > I'm using maven-release-plugin 2.0-beta9 and I'm still getting <scm> urls > rewritten at each deployment. > > http://jira.codehaus.org/browse/MRELEASE-231 is been closed quite a while > ago, so many we're not speaking about the same rewriting. > > The way we use the <SCM> tag in our organization is trough a parent pom > that > is suppose to set the <SCM> for each every child project. > > It looks like this: > <scm> > <connection>scm:svn:${svn.root}/trunk/${artifactId}</connection> > > > <developerConnection>scm:svn:${svn.root}/trunk/${artifactId}</developerConnection> > <url>${svn.root}/trunk/${artifactId}</url> > </scm> > > What I'm not getting is that while it's the only <SCM> tag in the whole > maven configuration, it gets rewritten at parent-pom deployment time WITH > parent-pom properties. > > Even though, when releasing a child project based on this parent release, > Release plugin seems to find it's way to our Subversion without any other > help. > > I really don't understand how this can possibly work. > Could somebody enlighten me on this? > > rgds > -jean > -- > View this message in context: > http://old.nabble.com/-Release--%3Cscm%3E-getting-rewritten.-how-does-it-work--tp26621596p26621596.html > Sent from the Maven - Users mailing list archive at Nabble.com. > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: users-unsubscr...@maven.apache.org > For additional commands, e-mail: users-h...@maven.apache.org > >
