Hi,
we've been using a definition of <scm> located in our company parent pom:
<scm>
<connection>scm:svn:${svn.root}/trunk/${artifactId}</connection>
<developerConnection>scm:svn:${svn.root}/trunk/${artifactId}</developerConnection>
<url>${svn.root}/trunk/${artifactId}</url>
</scm>
This used to work for all projects, even though we'd to manually
re-establish this after each release of the company pom, since the <scm> was
overwritten.
It seems to work in a totally fashion since the 2.0 release. The artifactId
seem to be added automatically at the end of the String. It wasn't like that
before.
But if we remove ${artifactId} from the string, the parent pom doesn't add
automatically it's own artifactId, which messes up big time in SVN when you
branch or release.
For now, I've started to add an <SCM> tag to each every subproject. But it's
heavy work that could be avoided.
Please let me know, doesn't it seems to be a legitimate requirement or am I
missing something?
cheers
--
View this message in context:
http://maven-users.828.n2.nabble.com/maven-release-plugin-using-scm-definition-in-parent-pom-for-all-project-tp4979515p4979515.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
