You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Craig Dickson (JIRA)" <ji...@codehaus.org> on 2006/06/06 16:38:43 UTC
[jira] Created: (MPRELEASE-19) SCM properties being replaced during
release:perform
SCM properties being replaced during release:perform
----------------------------------------------------
Key: MPRELEASE-19
URL: http://jira.codehaus.org/browse/MPRELEASE-19
Project: maven-release-plugin
Type: Bug
Environment: Windows XP client, Linux repo, CVS, Maven 2.0.4
Reporter: Craig Dickson
Attachments: after-release-perform-pom.xml, after-release-prepre-pom.xml, 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
[jira] Commented: (MRELEASE-128) SCM properties being replaced
during release:perform
Posted by "Michael Glauche (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MRELEASE-128?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=251297#action_251297 ]
Michael Glauche commented on MRELEASE-128:
------------------------------------------
For CVS it is kind of mission critical, you'll need to specify a scm username in the connection string, or otherwise the site plugin will crash. Hardcoding a name a la "svn@" does not work with cvs, so you really need a variable there if you have more than one user ...
> 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: Brett Porter
> Priority: Critical
> Fix For: 2.2
>
> 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
[jira] Commented: (MRELEASE-128) SCM properties being replaced
during release:perform
Posted by "Anthony Whitford (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MRELEASE-128?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=250913#action_250913 ]
Anthony Whitford commented on MRELEASE-128:
-------------------------------------------
*Has this issue really been open for more than _4 years_?*
This is a critical one for me; I am unable to adopt the latest release plugin until this is resolved.
I think this also impairs my progress towards Maven 3.
*I'd really appreciate this being resolved!* Thanks!
> 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: Brett Porter
> Priority: Critical
> Fix For: 2.2
>
> 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
[jira] Updated: (MRELEASE-128) SCM properties being replaced during
release:perform
Posted by "Mark Struberg (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MRELEASE-128?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Mark Struberg updated MRELEASE-128:
-----------------------------------
Fix Version/s: (was: 2.1)
2.2
> 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: Brett Porter
> Priority: Critical
> Fix For: 2.2
>
> 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
[jira] Commented: (MRELEASE-128) SCM properties being replaced
during release:perform
Posted by "Joerg Schaible (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MRELEASE-128?page=comments#action_67943 ]
Joerg Schaible commented on MRELEASE-128:
-----------------------------------------
Same for SVN. The plugin should restore the original entries in the trunk (HEAD revision) again.
> SCM properties being replaced during release:perform
> ----------------------------------------------------
>
> Key: MRELEASE-128
> URL: http://jira.codehaus.org/browse/MRELEASE-128
> Project: Maven 2.x Release Plugin
> Type: Bug
> Environment: Windows XP client, Linux repo, CVS, Maven 2.0.4
> Reporter: Craig Dickson
> Attachments: after-release-perform-pom.xml, after-release-prepre-pom.xml, 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
[jira] Commented: (MRELEASE-128) SCM properties being replaced
during release:perform
Posted by "Jan Ruzicka (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MRELEASE-128?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=225382#action_225382 ]
Jan Ruzicka commented on MRELEASE-128:
--------------------------------------
Is there anything preventing the attached patch to be committed?
> 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.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
[jira] Issue Comment Edited: (MRELEASE-128) SCM properties being
replaced during release:perform
Posted by "Torben Giesselmann (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MRELEASE-128?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=129909#action_129909 ]
torbengee edited comment on MRELEASE-128 at 4/5/08 2:56 PM:
---------------------------------------------------------------------
Here's a patch which fixes the problems for pom.xml.next and pom.xml.tag:
[^MNG-128-maven-release-manager.patch]
Branching is not (yet) supported.
It works like this: instead of using {{scm.getConnection()}} and {{scm.getDeveloperConnection()}} (which both contain the resolved variables), it uses the original text contained in pom.xml (using the XML element).
HOWEVER ... the tests for {{RewritePomsForDevelopmentPhase}} fail. I don't know exactly what's going on, but ... hmm, could the tests be wrong? (This is a silly assumption, I know, but ... well, I just don't know.)
Still, after patching you can install {{maven-release-manager}} with
{{mvn -Dmaven.test.skip=true clean install}}
and see if it works for you, too.
was (Author: torbengee):
Here's a patch which fixes the problems for pom.xml.next and pom.xml.tag.
Branching is not (yet) supported.
It works like this: instead of using {{scm.getConnection()}} and {{scm.getDeveloperConnection()}} (which both contain the resolved variables), it uses the original text contained in pom.xml (using the XML element).
HOWEVER ... the tests for {{RewritePomsForDevelopmentPhase}} fail. I don't know exactly what's going on, but ... hmm, could the tests be wrong? (This is a silly assumption, I know, but ... well, I just don't know.)
Still, after patching you can install {{maven-release-manager}} with
{{mvn -Dmaven.test.skip=true clean install}}
and see if it works for you, too.
> 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
> Environment: Windows XP client, Linux repo, CVS, Maven 2.0.4
> Reporter: Craig Dickson
> Assignee: Emmanuel Venisse
> Priority: Critical
> Fix For: 2.0
>
> 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
[jira] Commented: (MRELEASE-128) SCM properties being replaced
during release:perform
Posted by "Lars Fischer (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MRELEASE-128?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=224970#action_224970 ]
Lars Fischer commented on MRELEASE-128:
---------------------------------------
Hello,
is there a plan to fix this issue?
Regards,
Lars
> 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.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
[jira] Commented: (MRELEASE-128) SCM properties being replaced
during release:perform
Posted by "Stefan Seidel (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MRELEASE-128?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_113060 ]
Stefan Seidel commented on MRELEASE-128:
----------------------------------------
I agree. Just saying it is fixed doesn't make it so. We use ${USER} in the developerConnection (CVS) and it's being replaced too. Plugin version is 2.0-beta-6.
> 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
> Environment: Windows XP client, Linux repo, CVS, Maven 2.0.4
> Reporter: Craig Dickson
> Assignee: Emmanuel Venisse
> Priority: Critical
> Fix For: 2.0
>
> Attachments: after-release-perform-pom.xml, after-release-prepre-pom.xml, 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
[jira] (MRELEASE-128) SCM properties being replaced during
release:perform
Posted by "Robert Scholte (JIRA)" <ji...@codehaus.org>.
[ https://jira.codehaus.org/browse/MRELEASE-128?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Robert Scholte closed MRELEASE-128.
-----------------------------------
Resolution: Fixed
> SCM properties being replaced during release:perform
> ----------------------------------------------------
>
> Key: MRELEASE-128
> URL: https://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: Robert Scholte
> Priority: Critical
> Labels: properties
> Fix For: 2.3
>
> 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, please contact your JIRA administrators: https://jira.codehaus.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (MRELEASE-128) SCM properties being replaced during
release:perform
Posted by "Arnaud Heritier (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MRELEASE-128?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Arnaud Heritier updated MRELEASE-128:
-------------------------------------
Component/s: prepare
> 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
>
> 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
[jira] Commented: (MRELEASE-128) SCM properties being replaced
during release:perform
Posted by "jcrouvi (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MRELEASE-128?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=154758#action_154758 ]
jcrouvi commented on MRELEASE-128:
----------------------------------
Hi,
We are still experiencing this problem with the following configuration:
$ mvn --version
Maven version: 2.0.9
Java version: 1.6.0_07
OS name: "windows xp" version: "5.1" arch: "x86" Family: "windows"
org.apache.maven.plugins:maven-release-plugin:maven-plugin:2.0-beta-7:runtime
The POM files are changed after having called
mvn release:prepare
(not even a release:perform).
scm part in parent POM before release:prepare:
<scm>
<url>http://cvs.server.xx/cvs/test/continuous_integration/${project.artifactId}</url>
<developerConnection>${cvs.connection.test}continuous_integration/${project.artifactId}</developerConnection>
</scm>
scm part in parent POM AFTER release:prepare (properties have been replaced):
<scm>
<url>http://cvs.server.xx/cvs/test/continuous_integration/ipi-multimodule</url>
<developerConnection>scm:cvs|pserver|build_user@cvs.server.xx|/var/cvs/test|continuous_integration/ipi-multimodule</developerConnection>
</scm>
scm part in child POM before release:prepare:
<scm>
<url>${parent.scm.url}/${project.artifactId}</url>
</scm>
scm part in child POM AFTER release:prepare (properties have been replaced and a new line has been inserted; inheritance is broken!):
<scm>
<url>${parent.scm.url}/ipi-multimodule-a</url>
<developerConnection>scm:cvs|pserver|build_user@cvs.server.xx|/var/cvs/test|continuous_integration/ipi-multimodule-a/ipi-multimodule-a</developerConnection>
</scm>
> 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
> Environment: Windows XP client, Linux repo, CVS, Maven 2.0.4
> Reporter: Craig Dickson
> Assignee: Emmanuel Venisse
> Priority: Critical
> Fix For: 2.0
>
> 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
[jira] Commented: (MRELEASE-128) SCM properties being replaced
during release:perform
Posted by "Lars Fischer (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MRELEASE-128?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=239589#action_239589 ]
Lars Fischer commented on MRELEASE-128:
---------------------------------------
Hello,
I tried to use version 2.1 with this configuration:
<scm>
<connection>scm:svn:svn://${scm.host}/commons/trunk/xyz</connection>
<developerConnection>scm:svn:svn://${scm.host}/commons/trunk/xyz</developerConnection>
<url>http://${scm.host}/cgi-bin/viewvc.cgi/Commons</url>
</scm>
After releasing, the ${scm.host} in the new snapshot-pom was replaced by the ${scm.host}-value. Is there a way to keep the "${scm.host}"?
> 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: Brett Porter
> Priority: Critical
> Fix For: 2.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
[jira] Updated: (MRELEASE-128) SCM properties being replaced during
release:perform
Posted by "Jason van Zyl (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MRELEASE-128?page=all ]
Jason van Zyl updated MRELEASE-128:
-----------------------------------
Fix Version/s: 2.0-beta-5
> 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
> Environment: Windows XP client, Linux repo, CVS, Maven 2.0.4
> Reporter: Craig Dickson
> Assigned To: Jason van Zyl
> Fix For: 2.0-beta-5
>
> Attachments: after-release-perform-pom.xml, after-release-prepre-pom.xml, 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
[jira] Updated: (MRELEASE-128) SCM properties being replaced during
release:perform
Posted by "Torben Giesselmann (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MRELEASE-128?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Torben Giesselmann updated MRELEASE-128:
----------------------------------------
Attachment: MNG-128-maven-release-manager.patch
Here's a patch which fixes the problems for pom.xml.next and pom.xml.tag.
Branching is not (yet) supported.
It works like this: instead of using {{scm.getConnection()}} and {{scm.getDeveloperConnection()}} (which both contain the resolved variables), it uses the original text contained in pom.xml (using the XML element).
HOWEVER ... the tests for {{RewritePomsForDevelopmentPhase}} fail. I don't know exactly what's going on, but ... hmm, could the tests be wrong? (This is a silly assumption, I know, but ... well, I just don't know.)
Still, after patching you can install {{maven-release-manager}} with
{{mvn -Dmaven.test.skip=true clean install}}
and see if it works for you, too.
> 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
> Environment: Windows XP client, Linux repo, CVS, Maven 2.0.4
> Reporter: Craig Dickson
> Assignee: Emmanuel Venisse
> Priority: Critical
> Fix For: 2.0
>
> 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
[jira] Updated: (MRELEASE-128) SCM properties being replaced during
release:perform
Posted by "Carlos Sanchez (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MRELEASE-128?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Carlos Sanchez updated MRELEASE-128:
------------------------------------
Fix Version/s: (was: 2.0-beta-5)
> 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
> Environment: Windows XP client, Linux repo, CVS, Maven 2.0.4
> Reporter: Craig Dickson
> Assignee: Emmanuel Venisse
> Priority: Critical
> Attachments: after-release-perform-pom.xml, after-release-prepre-pom.xml, 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
[jira] (MRELEASE-128) SCM properties being replaced during
release:perform
Posted by "Robert Scholte (JIRA)" <ji...@codehaus.org>.
[ https://jira.codehaus.org/browse/MRELEASE-128?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=294665#comment-294665 ]
Robert Scholte commented on MRELEASE-128:
-----------------------------------------
Hi Gabriele,
Thanks for testing! Could you do me a favour and surround your logmessage with \{noformat} to make it easier to read.
You hit SCM-618 (which I already fixed), so that has nothing to do with my adjustment here.
My plan is to release this plugin with the next scm-version (1.7), so you shouldn't hit this problem by then.
> SCM properties being replaced during release:perform
> ----------------------------------------------------
>
> Key: MRELEASE-128
> URL: https://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: Robert Scholte
> Priority: Critical
> Labels: properties
> Fix For: 2.3
>
> 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, please contact your JIRA administrators: https://jira.codehaus.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Issue Comment Edited: (MRELEASE-128) SCM properties being
replaced during release:perform
Posted by "Stephane Nicoll (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MRELEASE-128?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_97045 ]
Stephane Nicoll edited comment on MRELEASE-128 at 5/25/07 2:52 AM:
-------------------------------------------------------------------
Brett,
It's very similar to the comment of Barrie Treloar. I have a ${maven.username} token in the developerConnection entry and it's replaced by release:prepare.
See this diff
{noformat}
[maven-release-plugin] prepare for next development iteration
Index: pom.xml
===================================================================
RCS file: /data/cvsroot/bar/pom.xml,v
retrieving revision 1.19.4.7
retrieving revision 1.19.4.8
diff -u -d -r1.19.4.7 -r1.19.4.8
--- pom.xml 23 May 2007 13:58:35 -0000 1.19.4.7
+++ pom.xml 23 May 2007 13:58:54 -0000 1.19.4.8
@@ -8,7 +8,7 @@
</parent>
<groupId>com.foo.shared.bar</groupId>
<artifactId>ionic-bar</artifactId>
- <version>5.5.5</version>
+ <version>5.5.6-SNAPSHOT</version>
<packaging>jar</packaging>
<inceptionYear>2007</inceptionYear>
<name>bar</name>
@@ -296,8 +296,8 @@
<scm>
<connection>scm:cvs:pserver:anonymous:blablabla@cvsserver:/data/cvsroot:bar</connection>
- <developerConnection>scm:cvs:pserver:$\{maven.username\}@cvsserver:/data/cvsroot:bar</developerConnection>
+ <developerConnection>scm:cvs:pserver:maven@cvsserver:/data/cvsroot:bar</developerConnection>
<url>http://intranet/cgi-bin/viewcvs.cgi/bar/</url>
- <tag>V5_5_5</tag>
+ <tag>RSE341</tag>
</scm>
</project>
{noformat}
SCM is CVS of course.
was:
Brett,
It's very similar to the comment of Barrie Treloar. I have a ${maven.username} token in the developerConnection entry and it's replaced by release:prepare.
See this diff
{noformat}
[maven-release-plugin] prepare for next development iteration
Index: pom.xml
===================================================================
RCS file: /data/cvsroot/bar/pom.xml,v
retrieving revision 1.19.4.7
retrieving revision 1.19.4.8
diff -u -d -r1.19.4.7 -r1.19.4.8
--- pom.xml 23 May 2007 13:58:35 -0000 1.19.4.7
+++ pom.xml 23 May 2007 13:58:54 -0000 1.19.4.8
@@ -8,7 +8,7 @@
</parent>
<groupId>com.foo.shared.bar</groupId>
<artifactId>ionic-bar</artifactId>
- <version>5.5.5</version>
+ <version>5.5.6-SNAPSHOT</version>
<packaging>jar</packaging>
<inceptionYear>2007</inceptionYear>
<name>bar</name>
@@ -296,8 +296,8 @@
<scm>
<connection>scm:cvs:pserver:anonymous:blablabla@cvsserver:/data/cvsroot:bar</connection>
- <developerConnection>scm:cvs:pserver:${maven.username}@cvsserver:/data/cvsroot:bar</developerConnection>
+ <developerConnection>scm:cvs:pserver:maven@cvsserver:/data/cvsroot:bar</developerConnection>
<url>http://intranet/cgi-bin/viewcvs.cgi/bar/</url>
- <tag>V5_5_5</tag>
+ <tag>RSE341</tag>
</scm>
</project>
{noformat}
SCM is CVS of course.
> 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
> Environment: Windows XP client, Linux repo, CVS, Maven 2.0.4
> Reporter: Craig Dickson
> Assignee: Emmanuel Venisse
> Priority: Critical
> Fix For: 2.0-beta-5
>
> Attachments: after-release-perform-pom.xml, after-release-prepre-pom.xml, 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
[jira] Commented: (MRELEASE-128) SCM properties being replaced
during release:perform
Posted by "Eric Bernstein (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MRELEASE-128?page=comments#action_74301 ]
Eric Bernstein commented on MRELEASE-128:
-----------------------------------------
I'm attaching a possible fix for this issue to MRELEASE-114. I had meant to post it here (which is why it's named as such), but apparently I have issue keeping track of my firefox tabs. The below notes are identical to my comments on MRELEASE-114.
Some notes:
1. I made the assumption that the only reason we rewrite the scm config is for subversion. This is quite possibly not the case, but it passed all the unit tests and made my CVS scm do what I wanted it to. This is probably not the way it should be implemented, but I don't know enough about the other SCMs to know if the rewrite is a special case or the non-rewrite is a special case.
2. This is a patch from the 2.0-beta-4 tag because the trunk didn't install cleanly on checkout - it may or may not be easily portable to the trunk.
> 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
> Environment: Windows XP client, Linux repo, CVS, Maven 2.0.4
> Reporter: Craig Dickson
> Attachments: after-release-perform-pom.xml, after-release-prepre-pom.xml, 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
[jira] Commented: (MRELEASE-128) SCM properties being replaced
during release:perform
Posted by "Markku Saarela (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MRELEASE-128?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=239921#action_239921 ]
Markku Saarela commented on MRELEASE-128:
-----------------------------------------
Also Maven 2.2.1 with 2.1 version doesn't work correctly.
> 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: Brett Porter
> Priority: Critical
> Fix For: 2.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
[jira] Commented: (MRELEASE-128) SCM properties being replaced
during release:perform
Posted by "Brett Porter (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MRELEASE-128?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_97040 ]
Brett Porter commented on MRELEASE-128:
---------------------------------------
Stephane - was is the difference between the test cases and your environment?
Just wondering if this was actually fixed for a certain set of cases (and a new issue needs to be opened), or not fixed at all (and so the fix version needs to be changed)
> 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
> Environment: Windows XP client, Linux repo, CVS, Maven 2.0.4
> Reporter: Craig Dickson
> Assignee: Emmanuel Venisse
> Priority: Critical
> Fix For: 2.0-beta-5
>
> Attachments: after-release-perform-pom.xml, after-release-prepre-pom.xml, 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
[jira] Commented: (MRELEASE-128) SCM properties being replaced
during release:perform
Posted by "Michael Wenig (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MRELEASE-128?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=196553#action_196553 ]
Michael Wenig commented on MRELEASE-128:
----------------------------------------
As we are currently moving some projects from cvs to subversion I recognized that the patch
MRELEASE-128_cvs_hack_RewritePomsForDevelopmentPhase.java.patch
is only valid for CVS. When using svn the patch may not be used as otherwise the poms left in the trunk/branch will then include the tagname. So I did put around two ifs in RewritePomsForDevelopmentPhase, checking if it is scm:cvs:
if ( scm != null )
{
String connection = scm.getConnection();
String developerConnection = scm.getDeveloperConnection();
if ((connection != null) && (connection.startsWith("scm:cvs:"))) {
//MRELEASE-128
String oldConnection = connection;
connection = ( scmRoot.getChildText("connection", namespace) != null )
? scmRoot.getChildText("connection", namespace)
: scm.getConnection();
getLogger().info("applying Patch MRELEASE-128 to connection, replacing " + oldConnection + " with " + connection);
}
if ((developerConnection != null) && (developerConnection.startsWith("scm:cvs:"))) {
//MRELEASE-128
String oldConnection = developerConnection;
developerConnection = ( scmRoot.getChildText("developerConnection", namespace) != null )
? scmRoot.getChildText("developerConnection", namespace)
: scm.getDeveloperConnection();
getLogger().info("applying Patch MRELEASE-128 to developerConnection, replacing " + oldConnection + " with " + connection);
}
rewriteElement( "connection", connection, scmRoot, namespace );
rewriteElement( "developerConnection", developerConnection, scmRoot, namespace );
rewriteElement( "url", scm.getUrl(), scmRoot, namespace );
rewriteElement( "tag", translator.resolveTag( scm.getTag() ), scmRoot, namespace );
(sorry - I am currently not able to create a patch-file for this as we have reversioned the source in our corporate system and it would not be applyable to the 'official' branch). It should be (after applying the patch mentioned above in src/main/java/org/apache/maven/shared/release/phase/RewritePomsForDevelopmentPhase.java
around line 72
now it seems to work with both cvs and svn.
When I am at home I will try to apply this to a 'fresh' checkout from the branch and create a real patch-file
> 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
>
> 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
[jira] (MRELEASE-128) SCM properties being replaced during
release:perform
Posted by "Gabriele (JIRA)" <ji...@codehaus.org>.
[ https://jira.codehaus.org/browse/MRELEASE-128?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=294609#comment-294609 ]
Gabriele commented on MRELEASE-128:
-----------------------------------
I've just tryed the 2.3-SNAPSHOT, it does work for scm URL under svn when executing prepare goal:
<connection>scm:svn:${project.scm.url}trunk</connection>
<developerConnection>${project.scm.connection}</developerConnection>
but when executing perform goal:
[ERROR] Failed to execute goal org.apache.maven.plugins:maven-release-plugin:2.3
-SNAPSHOT:perform (default-cli) on project BatchSistemaInformativo: An error is
occurred in the checkout process: Exception while executing SCM command. Error w
hile executing command. Error inside systemOut parser: String index out of range
: -1 -> [Help 1]
org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute goal o
rg.apache.maven.plugins:maven-release-plugin:2.3-SNAPSHOT:perform (default-cli)
on project BatchSistemaInformativo: An error is occurred in the checkout process
: Exception while executing SCM command.
at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:217)
at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:153)
at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:145)
at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:84)
at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:59)
at org.apache.maven.lifecycle.internal.LifecycleStarter.singleThreadedBuild(LifecycleStarter.java:183)
at org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:161)
at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:319)
at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:156)
at org.apache.maven.cli.MavenCli.execute(MavenCli.java:534)
at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:196)
at org.apache.maven.cli.MavenCli.main(MavenCli.java:141)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:290)
at org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:230)
at org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:409)
at org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:352)
Caused by: org.apache.maven.plugin.MojoExecutionException: An error is occurred in the checkout process: Exception while executing SCM command.
at org.apache.maven.plugins.release.PerformReleaseMojo.execute(PerformReleaseMojo.java:153)
at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:107)
at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:209)
... 19 more
Caused by: org.apache.maven.shared.release.ReleaseExecutionException: An error is occurred in the checkout process: Exception while executing SCM command.
at org.apache.maven.shared.release.phase.CheckoutProjectFromScm.execute(CheckoutProjectFromScm.java:133)
at org.apache.maven.shared.release.DefaultReleaseManager.perform(DefaultReleaseManager.java:421)
at org.apache.maven.shared.release.DefaultReleaseManager.perform(DefaultReleaseManager.java:373)
at org.apache.maven.plugins.release.PerformReleaseMojo.execute(PerformReleaseMojo.java:149)
... 21 more
Caused by: org.apache.maven.scm.ScmException: Exception while executing SCM command.
at org.apache.maven.scm.command.AbstractCommand.execute(AbstractCommand.java:63)
at org.apache.maven.scm.provider.svn.AbstractSvnScmProvider.executeCommand(AbstractSvnScmProvider.java:356)
at org.apache.maven.scm.provider.svn.AbstractSvnScmProvider.checkout(AbstractSvnScmProvider.java:292)
at org.apache.maven.scm.provider.AbstractScmProvider.checkOut(AbstractScmProvider.java:480)
at org.apache.maven.scm.provider.AbstractScmProvider.checkOut(AbstractScmProvider.java:453)
at org.apache.maven.shared.release.phase.CheckoutProjectFromScm.performCheckout(CheckoutProjectFromScm.java:208)
at org.apache.maven.shared.release.phase.CheckoutProjectFromScm.execute(CheckoutProjectFromScm.java:125)
... 24 more
Caused by: org.apache.maven.scm.ScmException: Error while executing command.
at org.apache.maven.scm.provider.svn.svnexe.command.checkout.SvnCheckOutCommand.executeCheckOutCommand(SvnCheckOutCommand.java:95)
at org.apache.maven.scm.command.checkout.AbstractCheckOutCommand.executeCommand(AbstractCheckOutCommand.java:82)
at org.apache.maven.scm.command.AbstractCommand.execute(AbstractCommand.java:59)
... 30 more
Caused by: org.codehaus.plexus.util.cli.CommandLineException: Error inside systemOut parser
at org.codehaus.plexus.util.cli.CommandLineUtils$1.call(CommandLineUtils.java:194)
at org.codehaus.plexus.util.cli.CommandLineUtils.executeCommandLine(CommandLineUtils.java:113)
at org.codehaus.plexus.util.cli.CommandLineUtils.executeCommandLine(CommandLineUtils.java:79)
at org.apache.maven.scm.provider.svn.svnexe.command.SvnCommandLineUtils.execute(SvnCommandLineUtils.java:146)
at org.apache.maven.scm.provider.svn.svnexe.command.checkout.SvnCheckOutCommand.executeCheckOutCommand(SvnCheckOutCommand.java:91)
... 32 more
Caused by: java.lang.StringIndexOutOfBoundsException: String index out of range: -1
at java.lang.String.substring(String.java:1937)
at java.lang.String.substring(String.java:1904)
at org.apache.maven.scm.provider.svn.svnexe.command.checkout.SvnCheckOutConsumer.parseLine(SvnCheckOutConsumer.java:57)
at org.apache.maven.scm.provider.svn.svnexe.command.AbstractFileCheckingConsumer.consumeLine(AbstractFileCheckingConsumer.java:68)
at org.codehaus.plexus.util.cli.StreamPumper.consumeLine(StreamPumper.java:190)
at org.codehaus.plexus.util.cli.StreamPumper.run(StreamPumper.java:135)
[ERROR]
[ERROR]
[ERROR] For more information about the errors and possible solutions, please read the following articles:
[ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/MojoExecutionException
> SCM properties being replaced during release:perform
> ----------------------------------------------------
>
> Key: MRELEASE-128
> URL: https://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: Robert Scholte
> Priority: Critical
> Labels: properties
> Fix For: 2.3
>
> 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, please contact your JIRA administrators: https://jira.codehaus.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Reopened: (MRELEASE-128) SCM properties being replaced
during release:perform
Posted by "Stephane Nicoll (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MRELEASE-128?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Stephane Nicoll reopened MRELEASE-128:
--------------------------------------
Tested on my first release with beta-5 and the scm url is still badly updated.
:(
> 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
> Environment: Windows XP client, Linux repo, CVS, Maven 2.0.4
> Reporter: Craig Dickson
> Assignee: Emmanuel Venisse
> Fix For: 2.0-beta-5
>
> Attachments: after-release-perform-pom.xml, after-release-prepre-pom.xml, 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
[jira] Issue Comment Edited: (MRELEASE-128) SCM properties being
replaced during release:perform
Posted by "Steve Tarver (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MRELEASE-128?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=150804#action_150804 ]
starver edited comment on MRELEASE-128 at 10/20/08 4:38 PM:
-----------------------------------------------------------------
Emmanuel,
I believe this is still broken in RewritePomsForDevelopmentPhase.transformScm(). The RewritePomsForReleasePhase.transformScm() works fine (note releaseConfiguration.mapOriginalScmInfo( projectId, project.getScm() );) , but values after string substitution are still used when prepping for the next development phase.
Here are changes on my pom that were committed to cvs over the prepare-perform cycle (replaced some parts with <...>)
Note the ${scm.username} is replaced with starver
<scm>
<connection>scm:cvs:ext:${scm.username}@<...></connection>
<developerConnection>scm:cvs:ext:${scm.username}@<...></developerConnection>
<url>http://vntwb1da.it.foo.net/cvsweb/cvsweb.cgi/<...>/oss-ticket-api/</url>
</scm>
<scm>
<connection>scm:cvs:ext:${scm.username}@<...></connection>
<developerConnection>scm:cvs:ext:${scm.username}@<...></developerConnection>
<url>http://vntwb1da.it.foo.net/cvsweb/cvsweb.cgi/<...>/oss-ticket-api/</url>
<tag>oss-ticket-api-1_0_29</tag>
</scm>
<scm>
<connection>scm:cvs:ext:starver@<...></connection>
<developerConnection>scm:cvs:ext:starver@<...></developerConnection>
<url>http://vntwb1da.it.foo.net/cvsweb/cvsweb.cgi/<...>/oss-ticket-api/</url>
</scm>
was (Author: starver):
Emmanuel,
I believe this is still broken in RewritePomsForDevelopmentPhase.transformScm(). The RewritePomsForReleasePhase.transformScm() works fine (note releaseConfiguration.mapOriginalScmInfo( projectId, project.getScm() );) , but values after string substitution are still used when prepping for the next development phase.
Here are changes on my pom that were committed to cvs over the prepare-perform cycle (replaced some parts with <...>)
<scm>
<connection>scm:cvs:ext:${scm.username}@<...></connection>
<developerConnection>scm:cvs:ext:${scm.username}@<...></developerConnection>
<url>http://vntwb1da.it.foo.net/cvsweb/cvsweb.cgi/<...>/oss-ticket-api/</url>
</scm>
<scm>
<connection>scm:cvs:ext:${scm.username}@<...></connection>
<developerConnection>scm:cvs:ext:${scm.username}@<...></developerConnection>
<url>http://vntwb1da.it.foo.net/cvsweb/cvsweb.cgi/<...>/oss-ticket-api/</url>
<tag>oss-ticket-api-1_0_29</tag>
</scm>
<scm>
<connection>scm:cvs:ext:starver@<...></connection>
<developerConnection>scm:cvs:ext:starver@<...></developerConnection>
<url>http://vntwb1da.it.foo.net/cvsweb/cvsweb.cgi/<...>/oss-ticket-api/</url>
</scm>
> 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
> Environment: Windows XP client, Linux repo, CVS, Maven 2.0.4
> Reporter: Craig Dickson
> Assignee: Emmanuel Venisse
> Priority: Critical
> Fix For: 2.0
>
> 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
[jira] Commented: (MRELEASE-128) SCM properties being replaced
during release:perform
Posted by "Stephane Nicoll (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MRELEASE-128?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_97046 ]
Stephane Nicoll commented on MRELEASE-128:
------------------------------------------
and forget the \ between the { (otherwise the formating is screwed).
> 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
> Environment: Windows XP client, Linux repo, CVS, Maven 2.0.4
> Reporter: Craig Dickson
> Assignee: Emmanuel Venisse
> Priority: Critical
> Fix For: 2.0-beta-5
>
> Attachments: after-release-perform-pom.xml, after-release-prepre-pom.xml, 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
[jira] Commented: (MRELEASE-128) SCM properties being replaced
during release:perform
Posted by "Torben Knerr (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MRELEASE-128?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=206949#action_206949 ]
Torben Knerr commented on MRELEASE-128:
---------------------------------------
+1 for fixing this bug.
The ticket says "Fix Version/s: 2.0.1". Is it now really fixed in 2.0.1?
Are you planning to release a fixed version soon? If it's fixed and tagged in svn I would not bother to build it myself...
> 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
[jira] Commented: (MRELEASE-128) SCM properties being replaced
during release:perform
Posted by "werner mueller (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MRELEASE-128?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=250968#action_250968 ]
werner mueller commented on MRELEASE-128:
-----------------------------------------
well a lot of plugins have this issue as well. The properties in its original form cannot be read via the plugin api (as far as i know). You can only retrieve them in the replaced way. So any plugin that rewrites the pom runs into this.
from what i know from the plugin it parses the pom.xml manually and replaces the strings 'by hand'. Which in my eyes is more tricky than one would think (depends on what part you replace with properties, your project layout, if you tag or branch or release, ...?)
But how can this be mission critical? It never 'worked' or has been this way. The release plugin (using svn in my case) needs these three lines in the scm, tabBase and branchBase are constant. In my eyes this features serves some readability in the pom and allows infrastructure changes without touching the pom files. If you do that a lot you're doomed anyway :)
> 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: Brett Porter
> Priority: Critical
> Fix For: 2.2
>
> 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
[jira] Issue Comment Edited: (MRELEASE-128) SCM properties being
replaced during release:perform
Posted by "Stanley Brubaker (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MRELEASE-128?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=246278#action_246278 ]
Stanley Brubaker edited comment on MRELEASE-128 at 12/3/10 9:33 AM:
--------------------------------------------------------------------
Maven 2.2.1, maven-release-plugin 2.1.
I've put the following in our super pom to give developers a pattern for all projects without having to configure scm in every child pom. We also have the svn host to be set in the settings.xml file:
{noformat}<scm>
<connection>scm:svn:http://${scm.host}/svn/${project.artifactId}/trunk/</connection>
<developerConnection>scm:svn:http://${scm.host}/svn/${project.artifactId}/trunk/</developerConnection>
<url>http://${scm.host}/viewvc/${project.artifactId}/trunk/</url>
</scm>
{noformat}
This works fine during development. When we run release:prepare, the checked-in tag pom.xml looks like this:
{noformat}<scm>
<connection>scm:svn:http://${scm.host}/svn/${project.artifactId}/tags/our-super-pom-1.0</connection>
<developerConnection>scm:svn:http://${scm.host}/svn/${project.artifactId}/tags/our-super-pom-1.0</developerConnection>
<url>http://${scm.host}/viewvc/${project.artifactId}/tags/our-super-pom-1.0</url>
</scm>
{noformat}
This is incorrect. If I expect to point child poms to the released parent, the scm section should remain the same as it was.
Also, the new snapshot pom.xml is changed to this:
{noformat}<scm>
<connection>scm:svn:http://host.company.net/svn/our-super-pom/trunk/</connection>
<developerConnection>scm:svn:http://host.company.net/svn/our-super-pom/trunk/</developerConnection>
<url>http://host.company.net/viewvc/our-super-pom/trunk/</url>
</scm>
{noformat}
This is incorrect. The next version of the pom.xml should be left alone, except for the version changing to 1.1-SNAPSHOT. Since we release our parent poms like everything else, there is no reason to modify anything besides the versions during the release process. Can we not have a property the disables substitutions altogether?
was (Author: sbrubaker):
Maven 2.2.1, maven-release-plugin 2.1.
I've put the following in our super pom to give developers a pattern for all projects without having to configure scm in every child pom. We also have the svn host to be set in the settings.xml file:
{noformat}<scm>
<connection>scm:svn:http://${scm.host}/svn/${project.artifactId}/trunk/</connection>
<developerConnection>scm:svn:http://${scm.host}/svn/${project.artifactId}/trunk/</developerConnection>
<url>http://${scm.host}/viewvc/${project.artifactId}/trunk/</url>
</scm>
{noformat}
This works fine during development. When we run release:prepare, the checked-in tag pom.xml looks like this:
{noformat}<scm>
<connection>scm:svn:http://${scm.host}/svn/${project.artifactId}/tags/our-super-pom-1.0</connection>
<developerConnection>scm:svn:http://${scm.host}/svn/${project.artifactId}/tags/our-super-pom-1.0</developerConnection>
<url>http://${scm.host}/viewvc/${project.artifactId}/tags/our-super-pom-1.0</url>
</scm>
{noformat}
This is correct. However the new snapshot pom.xml is changed to this:
{noformat}<scm>
<connection>scm:svn:http://host.company.net/svn/our-super-pom/trunk/</connection>
<developerConnection>scm:svn:http://host.company.net/svn/our-super-pom/trunk/</developerConnection>
<url>http://host.company.net/viewvc/our-super-pom/trunk/</url>
</scm>
{noformat}
This is incorrect. The next version of the pom.xml should be left alone, except for the version changing to 1.1-SNAPSHOT. Since we release our parent poms like everything else, there is no reason to modify anything besides the version and tag name during the release process.
> 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: Brett Porter
> Priority: Critical
> Fix For: 2.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
[jira] Commented: (MRELEASE-128) SCM properties being replaced
during release:perform
Posted by "Michael Glauche (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MRELEASE-128?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=233202#action_233202 ]
Michael Glauche commented on MRELEASE-128:
------------------------------------------
I think i found some workaround at least for the username/password issue:
First, remove the parameters from the SCM url like this:
{code}
<scm>
<connection>scm:cvs:pserver:cvsserver:/home/cvs/repository/test:test</connection>
</scm>
{code}
This way only works if you supply the release plugin with an username/password, like -Dusername=...
Fortunately you can set it in the build section like this:
{code}
<build>
<plugins>
<plugin>
<groupId>org.apache.maven.plugins</groupId>
<artifactId>maven-release-plugin</artifactId>
<configuration>
<username>${maven.scm.username}</username>
<password>${maven.scm.password}</password>
</configuration>
</plugin>
</plugins>
</build>
{code}
Then you just need to define maven.scm.username and password in your local settings and things start to look better :)
> 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.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
[jira] Commented: (MRELEASE-128) SCM properties being replaced
during release:perform
Posted by "Eric Bernstein (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MRELEASE-128?page=comments#action_74282 ]
Eric Bernstein commented on MRELEASE-128:
-----------------------------------------
I experienced this problem but with release:prepare, not release:perform. To the best of my knowledge, release:perform shouldn't be modifying any checked-in code. It simply checks out the configured tag and runs whatever goals it's configured to run (like deploy, deploy-site).
FYI - this seems very related to http://jira.codehaus.org/browse/MRELEASE-114. Someone with edit permission may want to combine this issue, http://jira.codehaus.org/browse/MRELEASE-114 and http://jira.codehaus.org/browse/MRELEASE-16.
> 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
> Environment: Windows XP client, Linux repo, CVS, Maven 2.0.4
> Reporter: Craig Dickson
> Attachments: after-release-perform-pom.xml, after-release-prepre-pom.xml, 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
[jira] Closed: (MRELEASE-128) SCM properties being replaced during
release:perform
Posted by "Brett Porter (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MRELEASE-128?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Brett Porter closed MRELEASE-128.
---------------------------------
Resolution: Fixed
Assignee: Brett Porter (was: Emmanuel Venisse)
Committed a fix in r1002124.
I think Torben's patch would have worked, but I instead used the project.getOriginalModel() for transforming the SCM elements, since that also retrieves the ones set by Maven before applying interpolation.
> 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: Brett Porter
> Priority: Critical
> Fix For: 2.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
[jira] Commented: (MRELEASE-128) SCM properties being replaced
during release:perform
Posted by "Stephane Nicoll (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MRELEASE-128?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_97045 ]
Stephane Nicoll commented on MRELEASE-128:
------------------------------------------
Brett,
It's very similar to the comment of Barrie Treloar. I have a ${maven.username} token in the developerConnection entry and it's replaced by release:prepare.
See this diff
{noformat}
[maven-release-plugin] prepare for next development iteration
Index: pom.xml
===================================================================
RCS file: /data/cvsroot/bar/pom.xml,v
retrieving revision 1.19.4.7
retrieving revision 1.19.4.8
diff -u -d -r1.19.4.7 -r1.19.4.8
--- pom.xml 23 May 2007 13:58:35 -0000 1.19.4.7
+++ pom.xml 23 May 2007 13:58:54 -0000 1.19.4.8
@@ -8,7 +8,7 @@
</parent>
<groupId>com.foo.shared.bar</groupId>
<artifactId>ionic-bar</artifactId>
- <version>5.5.5</version>
+ <version>5.5.6-SNAPSHOT</version>
<packaging>jar</packaging>
<inceptionYear>2007</inceptionYear>
<name>bar</name>
@@ -296,8 +296,8 @@
<scm>
<connection>scm:cvs:pserver:anonymous:blablabla@cvsserver:/data/cvsroot:bar</connection>
- <developerConnection>scm:cvs:pserver:${maven.username}@cvsserver:/data/cvsroot:bar</developerConnection>
+ <developerConnection>scm:cvs:pserver:maven@cvsserver:/data/cvsroot:bar</developerConnection>
<url>http://intranet/cgi-bin/viewcvs.cgi/bar/</url>
- <tag>V5_5_5</tag>
+ <tag>RSE341</tag>
</scm>
</project>
{noformat}
SCM is CVS of course.
> 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
> Environment: Windows XP client, Linux repo, CVS, Maven 2.0.4
> Reporter: Craig Dickson
> Assignee: Emmanuel Venisse
> Priority: Critical
> Fix For: 2.0-beta-5
>
> Attachments: after-release-perform-pom.xml, after-release-prepre-pom.xml, 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
[jira] Commented: (MRELEASE-128) SCM properties being replaced
during release:perform
Posted by "Markku Saarela (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MRELEASE-128?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=239920#action_239920 ]
Markku Saarela commented on MRELEASE-128:
-----------------------------------------
I confirms previous comment. With Maven 3.0 and and plugin version 2.1 I still get in scm element properties replaced with their actual values.
> 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: Brett Porter
> Priority: Critical
> Fix For: 2.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
[jira] Commented: (MRELEASE-128) SCM properties being replaced
during release:perform
Posted by "werner mueller (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MRELEASE-128?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=241606#action_241606 ]
werner mueller commented on MRELEASE-128:
-----------------------------------------
same here, maven 2.2.1, release-plugin 2.1 the scm properties are replaced.
{code}
<scm>
<connection>scm:svn:${svn.url}/Projekt</connection>
<developerConnection>scm:svn:${svn.url}/Projekt</developerConnection>
<url>${svn.url}/Projekt</url>
</scm>
{code}
> 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: Brett Porter
> Priority: Critical
> Fix For: 2.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
[jira] Commented: (MRELEASE-128) SCM properties being replaced
during release:perform
Posted by "Baerrach bonDierne (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MRELEASE-128?page=comments#action_83880 ]
Baerrach bonDierne commented on MRELEASE-128:
---------------------------------------------
I'm experiencing the same problem but with ${user.name}
{noformat}
<developerConnection>
scm:cvs:pserver:${user.name}@CVS_HOST:/cvs/CVS_ROOT:PROJECT_DIR
</developerConnection>
{noformat}
where the tagged release value is correct but the transformed version for the next snapshot is incorrect as $[user.name}
has been expanded to be the current users name.
This doesn't look like it is fixed by reading the patch attached to MRELEASE-114.
> 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
> Environment: Windows XP client, Linux repo, CVS, Maven 2.0.4
> Reporter: Craig Dickson
> Assigned To: Jason van Zyl
> Fix For: 2.0-beta-5
>
> Attachments: after-release-perform-pom.xml, after-release-prepre-pom.xml, 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
[jira] Issue Comment Edited: (MRELEASE-128) SCM properties being
replaced during release:perform
Posted by "Michael Glauche (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MRELEASE-128?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=233202#action_233202 ]
Michael Glauche edited comment on MRELEASE-128 at 8/26/10 3:19 AM:
-------------------------------------------------------------------
I think i found some workaround at least for the username/password issue:
First, remove the parameters from the SCM url like this:
{code}
<scm>
<connection>scm:cvs:pserver:cvsserver:/home/cvs/repository/test:test</connection>
</scm>
{code}
This way only works if you supply the release plugin with an username/password, like -Dusername=...
Fortunately you can set it in the build section like this:
{code}
<build>
<plugins>
<plugin>
<groupId>org.apache.maven.plugins</groupId>
<artifactId>maven-release-plugin</artifactId>
<configuration>
<username>${maven.scm.username}</username>
<password>${maven.scm.password}</password>
</configuration>
</plugin>
</plugins>
</build>
{code}
As the substitution only is broken inside the scm tag, this should work.
You just need to define maven.scm.username and password in your local settings and things start to look better :)
was (Author: mglauche):
I think i found some workaround at least for the username/password issue:
First, remove the parameters from the SCM url like this:
{code}
<scm>
<connection>scm:cvs:pserver:cvsserver:/home/cvs/repository/test:test</connection>
</scm>
{code}
This way only works if you supply the release plugin with an username/password, like -Dusername=...
Fortunately you can set it in the build section like this:
{code}
<build>
<plugins>
<plugin>
<groupId>org.apache.maven.plugins</groupId>
<artifactId>maven-release-plugin</artifactId>
<configuration>
<username>${maven.scm.username}</username>
<password>${maven.scm.password}</password>
</configuration>
</plugin>
</plugins>
</build>
{code}
Then you just need to define maven.scm.username and password in your local settings and things start to look better :)
> 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.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
[jira] Updated: (MRELEASE-128) SCM properties being replaced during
release:perform
Posted by "Arnaud Heritier (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MRELEASE-128?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Arnaud Heritier updated MRELEASE-128:
-------------------------------------
Testcase included: yes
Patch Submitted: [Yes]
> 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
>
> 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
[jira] Issue Comment Edited: (MRELEASE-128) SCM properties being
replaced during release:perform
Posted by "Michael Wenig (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MRELEASE-128?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=196553#action_196553 ]
Michael Wenig edited comment on MRELEASE-128 at 10/29/09 12:26 PM:
-------------------------------------------------------------------
As we are currently moving some projects from cvs to subversion I recognized that the patch
MRELEASE-128_cvs_hack_RewritePomsForDevelopmentPhase.java.patch
is only valid for CVS. When using svn the patch may not be used as otherwise the poms left in the trunk/branch will then include the tagname. So I did put around two ifs in RewritePomsForDevelopmentPhase, checking if it is scm:cvs:
{noformat}
if ( scm != null )
{
String connection = scm.getConnection();
String developerConnection = scm.getDeveloperConnection();
if ((connection != null) && (connection.startsWith("scm:cvs:"))) {
//MRELEASE-128
String oldConnection = connection;
connection = ( scmRoot.getChildText("connection", namespace) != null )
? scmRoot.getChildText("connection", namespace)
: scm.getConnection();
getLogger().info("applying Patch MRELEASE-128 to connection, replacing " + oldConnection + " with " + connection);
}
if ((developerConnection != null) && (developerConnection.startsWith("scm:cvs:"))) {
//MRELEASE-128
String oldConnection = developerConnection;
developerConnection = ( scmRoot.getChildText("developerConnection", namespace) != null )
? scmRoot.getChildText("developerConnection", namespace)
: scm.getDeveloperConnection();
getLogger().info("applying Patch MRELEASE-128 to developerConnection, replacing " + oldConnection + " with " + connection);
}
rewriteElement( "connection", connection, scmRoot, namespace );
rewriteElement( "developerConnection", developerConnection, scmRoot, namespace );
rewriteElement( "url", scm.getUrl(), scmRoot, namespace );
rewriteElement( "tag", translator.resolveTag( scm.getTag() ), scmRoot, namespace );
{noformat}
(sorry - I am currently not able to create a patch-file for this as we have reversioned the source in our corporate system and it would not be applyable to the 'official' branch). It should be (after applying the patch mentioned above in src/main/java/org/apache/maven/shared/release/phase/RewritePomsForDevelopmentPhase.java
around line 72
now it seems to work with both cvs and svn.
When I am at home I will try to apply this to a 'fresh' checkout from the branch and create a real patch-file
Edit: formatting
was (Author: micha123):
As we are currently moving some projects from cvs to subversion I recognized that the patch
MRELEASE-128_cvs_hack_RewritePomsForDevelopmentPhase.java.patch
is only valid for CVS. When using svn the patch may not be used as otherwise the poms left in the trunk/branch will then include the tagname. So I did put around two ifs in RewritePomsForDevelopmentPhase, checking if it is scm:cvs:
if ( scm != null )
{
String connection = scm.getConnection();
String developerConnection = scm.getDeveloperConnection();
if ((connection != null) && (connection.startsWith("scm:cvs:"))) {
//MRELEASE-128
String oldConnection = connection;
connection = ( scmRoot.getChildText("connection", namespace) != null )
? scmRoot.getChildText("connection", namespace)
: scm.getConnection();
getLogger().info("applying Patch MRELEASE-128 to connection, replacing " + oldConnection + " with " + connection);
}
if ((developerConnection != null) && (developerConnection.startsWith("scm:cvs:"))) {
//MRELEASE-128
String oldConnection = developerConnection;
developerConnection = ( scmRoot.getChildText("developerConnection", namespace) != null )
? scmRoot.getChildText("developerConnection", namespace)
: scm.getDeveloperConnection();
getLogger().info("applying Patch MRELEASE-128 to developerConnection, replacing " + oldConnection + " with " + connection);
}
rewriteElement( "connection", connection, scmRoot, namespace );
rewriteElement( "developerConnection", developerConnection, scmRoot, namespace );
rewriteElement( "url", scm.getUrl(), scmRoot, namespace );
rewriteElement( "tag", translator.resolveTag( scm.getTag() ), scmRoot, namespace );
(sorry - I am currently not able to create a patch-file for this as we have reversioned the source in our corporate system and it would not be applyable to the 'official' branch). It should be (after applying the patch mentioned above in src/main/java/org/apache/maven/shared/release/phase/RewritePomsForDevelopmentPhase.java
around line 72
now it seems to work with both cvs and svn.
When I am at home I will try to apply this to a 'fresh' checkout from the branch and create a real patch-file
> 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
>
> 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
[jira] Commented: (MRELEASE-128) SCM properties being replaced
during release:perform
Posted by "Sylvain Marié (JIRA)" <ji...@codehaus.org>.
[ 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
[jira] Issue Comment Edited: (MRELEASE-128) SCM properties being
replaced during release:perform
Posted by "Vadim Strizhevsky (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MRELEASE-128?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_121176 ]
vadim edited comment on MRELEASE-128 at 1/24/08 9:18 AM:
---------------------------------------------------------------------
I'm still seeing this issue with maven-release-plugin 2.0-beta-7. The pom in the tag is correct, but the final pom in the HEAD has ${user.name} expanded in the <scm> section.
was (Author: vadim):
I'm still seeing this issue with maven-release-plugin 2.0.7. The pom in the tag is correct, but the final pom in the HEAD has ${user.name} expanded in the <scm> section.
> 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
> Environment: Windows XP client, Linux repo, CVS, Maven 2.0.4
> Reporter: Craig Dickson
> Assignee: Emmanuel Venisse
> Priority: Critical
> Fix For: 2.0
>
> Attachments: after-release-perform-pom.xml, after-release-prepre-pom.xml, 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
[jira] Commented: (MRELEASE-128) SCM properties being replaced
during release:perform
Posted by "Steve Tarver (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MRELEASE-128?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=150804#action_150804 ]
Steve Tarver commented on MRELEASE-128:
---------------------------------------
Emmanuel,
I believe this is still broken in RewritePomsForDevelopmentPhase.transformScm(). The RewritePomsForReleasePhase.transformScm() works fine (note releaseConfiguration.mapOriginalScmInfo( projectId, project.getScm() );) , but values after string substitution are still used when prepping for the next development phase.
Here are changes on my pom that were committed to cvs over the prepare-perform cycle (replaced some parts with <...>)
<scm>
<connection>scm:cvs:ext:${scm.username}@<...></connection>
<developerConnection>scm:cvs:ext:${scm.username}@<...></developerConnection>
<url>http://vntwb1da.it.foo.net/cvsweb/cvsweb.cgi/<...>/oss-ticket-api/</url>
</scm>
<scm>
<connection>scm:cvs:ext:${scm.username}@<...></connection>
<developerConnection>scm:cvs:ext:${scm.username}@<...></developerConnection>
<url>http://vntwb1da.it.foo.net/cvsweb/cvsweb.cgi/<...>/oss-ticket-api/</url>
<tag>oss-ticket-api-1_0_29</tag>
</scm>
<scm>
<connection>scm:cvs:ext:starver@<...></connection>
<developerConnection>scm:cvs:ext:starver@<...></developerConnection>
<url>http://vntwb1da.it.foo.net/cvsweb/cvsweb.cgi/<...>/oss-ticket-api/</url>
</scm>
> 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
> Environment: Windows XP client, Linux repo, CVS, Maven 2.0.4
> Reporter: Craig Dickson
> Assignee: Emmanuel Venisse
> Priority: Critical
> Fix For: 2.0
>
> 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
[jira] Updated: (MRELEASE-128) SCM properties being replaced during
release:perform
Posted by "Stephane Nicoll (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MRELEASE-128?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Stephane Nicoll updated MRELEASE-128:
-------------------------------------
Fix Version/s: 2.0
> 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
> Environment: Windows XP client, Linux repo, CVS, Maven 2.0.4
> Reporter: Craig Dickson
> Assignee: Emmanuel Venisse
> Priority: Critical
> Fix For: 2.0
>
> Attachments: after-release-perform-pom.xml, after-release-prepre-pom.xml, 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
[jira] Commented: (MRELEASE-128) SCM properties being replaced
during release:perform
Posted by "Frédéric Camblor (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MRELEASE-128?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=241779#action_241779 ]
Frédéric Camblor commented on MRELEASE-128:
-------------------------------------------
+1
How could we "re-open" the issue ?
Looks like I don't have sufficient rights to do this.
> 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: Brett Porter
> Priority: Critical
> Fix For: 2.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
[jira] Reopened: (MRELEASE-128) SCM properties being replaced
during release:perform
Posted by "Stephane Nicoll (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MRELEASE-128?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Stephane Nicoll reopened MRELEASE-128:
--------------------------------------
> 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: Brett Porter
> Priority: Critical
> Fix For: 2.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
[jira] Commented: (MRELEASE-128) SCM properties being replaced
during release:perform
Posted by "Havard Bjastad (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MRELEASE-128?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=202125#action_202125 ]
Havard Bjastad commented on MRELEASE-128:
-----------------------------------------
Wow, this bug is THREE AND A HALF YEARS OLD and nobody has been able to fix it?
We're supposed to use Maven, but after all this time it's still not able to create a release without messing up the POMs?
> 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
>
> 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
[jira] Commented: (MRELEASE-128) SCM properties being replaced
during release:perform
Posted by "Russell (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MRELEASE-128?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=210251#action_210251 ]
Russell commented on MRELEASE-128:
----------------------------------
I'm having this problem, yet I notice this ticket has been open since June 2006
Is anyone looking at this? Is it fixed in 2.0.1? If so, will 2.0.1 be released soon?
> 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
[jira] (MRELEASE-128) SCM properties being replaced during
release:perform
Posted by "Robert Scholte (JIRA)" <ji...@codehaus.org>.
[ https://jira.codehaus.org/browse/MRELEASE-128?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Robert Scholte closed MRELEASE-128.
-----------------------------------
Resolution: Fixed
Assignee: Robert Scholte (was: Brett Porter)
Fixed in [rev.1302692|http://svn.apache.org/viewvc?rev=1302692&view=rev]
For those interested: the main reason why the release-pom was okay and the next-dev-pom not is because the release.pom was based on the originalModel of the MavenProject. The next-dev-pom uses the releases.properties, which used to contain the resolved properties. After analyzing this it seems that these property values are only used for rewriting the next-dev-pom.
So I've changed this, so the unresolved values are stored.
I've released a 2.3-SNAPSHOT for those who want to try this fix.
It would be nice if some could confirm this fix and that nothing is broken by this adjustment.
> SCM properties being replaced during release:perform
> ----------------------------------------------------
>
> Key: MRELEASE-128
> URL: https://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: Robert Scholte
> Priority: Critical
> Labels: properties
> Fix For: 2.3
>
> 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, please contact your JIRA administrators: https://jira.codehaus.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (MRELEASE-128) SCM properties being replaced during
release:perform
Posted by "Herve Boutemy (JIRA)" <ji...@codehaus.org>.
[ https://jira.codehaus.org/browse/MRELEASE-128?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Herve Boutemy updated MRELEASE-128:
-----------------------------------
Description:
The <scm> section of a pom in CVS for a pom archetype project looks like this prior to executing release:prepare :
{code:xml}<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>{code}
Then after executing release:prepare, the pom in CVS looks like this (new <tag> tag is only difference):
{code:xml}<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>{code}
Then after executing release:perform, the pom looks like this in CVS:
{code:xml}<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>{code}
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
was:
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
> SCM properties being replaced during release:perform
> ----------------------------------------------------
>
> Key: MRELEASE-128
> URL: https://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: Robert Scholte
> Priority: Critical
> Labels: properties
> Fix For: 2.3
>
> 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 :
> {code:xml}<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>{code}
> Then after executing release:prepare, the pom in CVS looks like this (new <tag> tag is only difference):
> {code:xml}<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>{code}
> Then after executing release:perform, the pom looks like this in CVS:
> {code:xml}<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>{code}
> 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, please contact your JIRA administrators: https://jira.codehaus.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (MRELEASE-128) SCM properties being replaced during
release:perform
Posted by "Stephen Connolly (JIRA)" <ji...@codehaus.org>.
[ https://jira.codehaus.org/browse/MRELEASE-128?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Stephen Connolly updated MRELEASE-128:
--------------------------------------
Fix Version/s: (was: 2.2)
2.3
Pushing back to 2.3 as this is a large scope of work, and there are some issues that we want to push 2.2 out for.
> SCM properties being replaced during release:perform
> ----------------------------------------------------
>
> Key: MRELEASE-128
> URL: https://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: Brett Porter
> Priority: Critical
> Labels: properties
> Fix For: 2.3
>
> 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.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Closed: (MRELEASE-128) SCM properties being replaced during
release:perform
Posted by "Emmanuel Venisse (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MRELEASE-128?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Emmanuel Venisse closed MRELEASE-128.
-------------------------------------
Assignee: Emmanuel Venisse (was: Jason van Zyl)
Resolution: Fixed
Already fixed.
> 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
> Environment: Windows XP client, Linux repo, CVS, Maven 2.0.4
> Reporter: Craig Dickson
> Assignee: Emmanuel Venisse
> Fix For: 2.0-beta-5
>
> Attachments: after-release-perform-pom.xml, after-release-prepre-pom.xml, 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
[jira] (MRELEASE-128) SCM properties being replaced during
release:perform
Posted by "rumi (JIRA)" <ji...@codehaus.org>.
[ https://jira.codehaus.org/browse/MRELEASE-128?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=286202#comment-286202 ]
rumi commented on MRELEASE-128:
-------------------------------
The same for git provider. SCM properties are not changed, project.scm.tag (git version) is not added/updated in particular.
May it may be caused by lack of GitScmTranslator ?
> SCM properties being replaced during release:perform
> ----------------------------------------------------
>
> Key: MRELEASE-128
> URL: https://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: Brett Porter
> Priority: Critical
> Labels: properties
> Fix For: 2.3
>
> 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, please contact your JIRA administrators: https://jira.codehaus.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (MRELEASE-128) SCM properties being replaced
during release:perform
Posted by "Martin Gilday (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MRELEASE-128?page=comments#action_67977 ]
Martin Gilday commented on MRELEASE-128:
----------------------------------------
I posted a question regarding this on the maven users mailing list. At least now I know it appears to be a bug and not my POM.
But I get the problem when using release:perform as well. Do I need to create another issue for this (quite new to JIRA/reporting)?
Another slight difference is that my property is for the SCM username and password - $\{cvs-user\} and $\{cvs-pass\}. After a release:perform both of these properties are replaced with the ones from the settings.xml. I have tried removing the properties from the POM and specifiying them with \ -Dusername and \-Dpassword. Doing this also reasults in the SCM path being altered and the login details added. Both the exported POM and the original POM are incorrectly altered.
{code:xml}
<scm>
<connection>scm:cvs:pserver:${cvs-user}:${cvs-pass}@10.0.0.3:/usr/share/cvs/cvsroot:MyProjectName</connection>
<developerConnection>scm:cvs:pserver:${cvs-user}:${cvs-pass}@10.0.0.3:/usr/share/cvs/cvsroot:MyProjectName</developerConnection>
</scm>
{code}
turns to
{code:xml}
<scm>
<connection>scm:cvs:pserver:joebloggs:p4ssw0rd@10.0.0.3:/usr/share/cvs/cvsroot:MyProjectName</connection>
<developerConnection>scm:cvs:pserver:joebloggs:p4ssw0rd@10.0.0.3:/usr/share/cvs/cvsroot:MyProjectName</developerConnection>
</scm>
{code}
after the release:perform is called.
> SCM properties being replaced during release:perform
> ----------------------------------------------------
>
> Key: MRELEASE-128
> URL: http://jira.codehaus.org/browse/MRELEASE-128
> Project: Maven 2.x Release Plugin
> Type: Bug
> Environment: Windows XP client, Linux repo, CVS, Maven 2.0.4
> Reporter: Craig Dickson
> Attachments: after-release-perform-pom.xml, after-release-prepre-pom.xml, 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
[jira] Updated: (MRELEASE-128) SCM properties being replaced during
release:perform
Posted by "Stephane Nicoll (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MRELEASE-128?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Stephane Nicoll updated MRELEASE-128:
-------------------------------------
Priority: Critical (was: Major)
> 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
> Environment: Windows XP client, Linux repo, CVS, Maven 2.0.4
> Reporter: Craig Dickson
> Assignee: Emmanuel Venisse
> Priority: Critical
> Fix For: 2.0-beta-5
>
> Attachments: after-release-perform-pom.xml, after-release-prepre-pom.xml, 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
[jira] Commented: (MRELEASE-128) SCM properties being replaced
during release:perform
Posted by "Stanley Brubaker (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MRELEASE-128?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=246278#action_246278 ]
Stanley Brubaker commented on MRELEASE-128:
-------------------------------------------
Maven 2.2.1, maven-release-plugin 2.1.
I've put the following in our super pom to give developers a pattern for all projects without having to configure scm in every child pom. We also have the svn host to be set in the settings.xml file:
{noformat}<scm>
<connection>scm:svn:http://${scm.host}/svn/${project.artifactId}/trunk/</connection>
<developerConnection>scm:svn:http://${scm.host}/svn/${project.artifactId}/trunk/</developerConnection>
<url>http://${scm.host}/viewvc/${project.artifactId}/trunk/</url>
</scm>
{noformat}
This works fine during development. When we run release:prepare, the checked-in tag pom.xml looks like this:
{noformat}<scm>
<connection>scm:svn:http://${scm.host}/svn/${project.artifactId}/tags/our-super-pom-1.0</connection>
<developerConnection>scm:svn:http://${scm.host}/svn/${project.artifactId}/tags/our-super-pom-1.0</developerConnection>
<url>http://${scm.host}/viewvc/${project.artifactId}/tags/our-super-pom-1.0</url>
</scm>
{noformat}
This is correct. However the new snapshot pom.xml is changed to this:
{noformat}<scm>
<connection>scm:svn:http://host.company.net/svn/our-super-pom/trunk/</connection>
<developerConnection>scm:svn:http://host.company.net/svn/our-super-pom/trunk/</developerConnection>
<url>http://host.company.net/viewvc/our-super-pom/trunk/</url>
</scm>
{noformat}
This is incorrect. The next version of the pom.xml should be left alone, except for the version changing to 1.1-SNAPSHOT. Since we release our parent poms like everything else, there is no reason to modify anything besides the version and tag name during the release process.
> 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: Brett Porter
> Priority: Critical
> Fix For: 2.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
[jira] Commented: (MRELEASE-128) SCM properties being replaced
during release:perform
Posted by "Vadim Strizhevsky (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MRELEASE-128?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_121176 ]
Vadim Strizhevsky commented on MRELEASE-128:
--------------------------------------------
I'm still seeing this issue with maven-release-plugin 2.0.7. The pom in the tag is correct, but the final pom in the HEAD has ${user.name} expanded in the <scm> section.
> 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
> Environment: Windows XP client, Linux repo, CVS, Maven 2.0.4
> Reporter: Craig Dickson
> Assignee: Emmanuel Venisse
> Priority: Critical
> Fix For: 2.0
>
> Attachments: after-release-perform-pom.xml, after-release-prepre-pom.xml, 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
[jira] (MRELEASE-128) SCM properties being replaced during
release:perform
Posted by "Robert Scholte (JIRA)" <ji...@codehaus.org>.
[ https://jira.codehaus.org/browse/MRELEASE-128?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Robert Scholte reopened MRELEASE-128:
-------------------------------------
> SCM properties being replaced during release:perform
> ----------------------------------------------------
>
> Key: MRELEASE-128
> URL: https://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: Robert Scholte
> Priority: Critical
> Labels: properties
> Fix For: 2.3
>
> 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, please contact your JIRA administrators: https://jira.codehaus.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (MRELEASE-128) SCM properties being replaced
during release:perform
Posted by "Stephane Nicoll (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MRELEASE-128?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_93407 ]
Stephane Nicoll commented on MRELEASE-128:
------------------------------------------
wonderful!
> 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
> Environment: Windows XP client, Linux repo, CVS, Maven 2.0.4
> Reporter: Craig Dickson
> Assignee: Emmanuel Venisse
> Fix For: 2.0-beta-5
>
> Attachments: after-release-perform-pom.xml, after-release-prepre-pom.xml, 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
[jira] Commented: (MRELEASE-128) SCM properties being replaced
during release:perform
Posted by "Barrie Treloar (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MRELEASE-128?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=250917#action_250917 ]
Barrie Treloar commented on MRELEASE-128:
-----------------------------------------
Anthony, it's open source. Feel free to roll up the sleeves and provide some help to get it resolved.
> 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: Brett Porter
> Priority: Critical
> Fix For: 2.2
>
> 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