[
http://jira.codehaus.org/browse/MRELEASE-128?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=211106#action_211106
]
Sylvain Marié commented on MRELEASE-128:
----------------------------------------
+1. But for us I don't think the property is enough ; indeed we would like
children pom to have their full path be configured correctly. If a
NON-AGGREGATOR parent project is configured as follows:
<!-- properties -->
<svnserver.prop>svn.com<svnserver.prop>
<path.prop>foo</path.prop>
<scm>
<connection>scm:svn:http://${svnserver.prop}/${path.prop}/${artifactId}/trunk/</developerConnection>
<developerConnection>scm:svn:http://${svnserver.prop}/${path.prop}/${artifactId}/trunk/</developerConnection>
<url>http://${svnserver.prop}/view/${path.prop}/${artifactId}/trunk/</url>
<scm>
then if releasing version 1, its release pom in the svn TAG will be (even
keeping the properties)
<!-- same properties -->
<scm>
<connection>scm:svn:http://${svnserver.prop}/${path.prop}/${artifactId}/tags/parent-pom-1/</developerConnection>
<developerConnection>scm:svn:http://${svnserver.prop}/${path.prop}/${artifactId}/tags/parent-pom-1/</developerConnection>
<url>http://${svnserver.prop}/view/${path.prop}/${artifactId}/tags/parent-pom-1/</url>
<scm>
I would like a child project also sitting on the same server to be able to
inherit most of the configuration.
What should I do ? Well even properties won't help it to inherit from the url
below, because its parent is a TAG.
So I have to rewrite all the scm section :
<scm>
<connection>scm:svn:http://${svnserver.prop}/${path.prop}/${artifactId}/trunk/</developerConnection>
<developerConnection>scm:svn:http://${svnserver.prop}/${path.prop}/${artifactId}/trunk/</developerConnection>
<url>http://${svnserver.prop}/view/${path.prop}/${artifactId}/trunk/</url>
<scm>
A major breakthrough would be to be able to set a RELATIVE SCM URL wrt the
parent's trunk. This would really ease the process, as a child would now write
<relative>../${artifactId}<relative>
Note that this url needs to be understood by maven SVN scm plugin - so I guess
this is more a Maven 3.x feature and not in scope of maven-release plugin...
regards
Sylvain
> SCM properties being replaced during release:perform
> ----------------------------------------------------
>
> Key: MRELEASE-128
> URL: http://jira.codehaus.org/browse/MRELEASE-128
> Project: Maven 2.x Release Plugin
> Issue Type: Bug
> Components: prepare
> Environment: Windows XP client, Linux repo, CVS, Maven 2.0.4
> Reporter: Craig Dickson
> Assignee: Emmanuel Venisse
> Priority: Critical
> Fix For: 2.0.1
>
> Attachments: after-release-perform-pom.xml,
> after-release-prepre-pom.xml, MNG-128-maven-release-manager.patch,
> MRELEASE-128_cvs_hack_RewritePomsForDevelopmentPhase.java.patch,
> original-pom.xml
>
>
> The <scm> section of a pom in CVS for a pom archetype project looks like this
> prior to executing release:prepare :
> <scm>
> <connection>${base.cvs.url}:commons-maven/uber-pom</connection>
>
> <developerConnection>${base.cvs.url}:commons-maven/uber-pom</developerConnection>
> <url>${base.viewcvs.url}/commons-maven/uber-pom</url>
> </scm>
> Then after executing release:prepare, the pom in CVS looks like this (new
> <tag> tag is only difference):
> <scm>
> <connection>${base.cvs.url}:commons-maven/uber-pom</connection>
>
> <developerConnection>${base.cvs.url}:commons-maven/uber-pom</developerConnection>
> <url>${base.viewcvs.url}/commons-maven/uber-pom</url>
> <tag>R-1_7</tag>
> </scm>
> Then after executing release:perform, the pom looks like this in CVS:
> <scm>
>
> <connection>scm:cvs:pserver:behrcvs.masco-coatings.com:/usr/cvsroot:commons-maven/uber-pom</connection>
>
> <developerConnection>scm:cvs:pserver:behrcvs.masco-coatings.com:/usr/cvsroot:commons-maven/uber-pom</developerConnection>
>
> <url>http://behrcvs.masco-coatings.com/cgi-bin/viewcvs.cgi/commons-maven/uber-pom</url>
> </scm>
> Notice that the properties that were there for the base URLs for CVS and
> ViewCVS have been replaced with literal values.
> No other properties in the POM are being replaced
--
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
