[
http://jira.codehaus.org/browse/MRELEASE-114?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=202127#action_202127
]
Havard Bjastad commented on MRELEASE-114:
-
Emmanuel, you're saying "Already fixed", but we'
[
http://jira.codehaus.org/browse/MRELEASE-114?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_93448
]
Ian Springer commented on MRELEASE-114:
---
I had ${maven.username} is the value of scm.developerConnection, and it was
[ http://jira.codehaus.org/browse/MRELEASE-114?page=comments#action_78411 ]
Eric Bernstein commented on MRELEASE-114:
-
Yes, Jurgen, that's where my patch falls short (see point 1 on my notes above).
I knew SVN needed some form of rewrite
[ http://jira.codehaus.org/browse/MRELEASE-114?page=comments#action_78409 ]
Jurgen Lust commented on MRELEASE-114:
--
I checked out the 2.0-beta-4 tag of the maven-release-plugin and applied the
patch supplied here, but the problem remains: ${
[ http://jira.codehaus.org/browse/MRELEASE-114?page=comments#action_74300 ]
Eric Bernstein commented on MRELEASE-114:
-
My bad, I named the patch for MRELEASE-128, but published it to MRELEASE-114.
Sorry about that. I do believe MRELEASE
[ http://jira.codehaus.org/browse/MRELEASE-114?page=comments#action_66975 ]
Richard van der Hoff commented on MRELEASE-114:
---
Yes it is, and it's very annoying.
Sounds like a duplicate of MRELEASE-16 to me.
> ${project.artifactId} was replaced
[ http://jira.codehaus.org/browse/MRELEASE-114?page=comments#action_65623 ]
Paul Spencer commented on MRELEASE-114:
---
The tag inside the tag is also affected by this bug.
> ${project.artifactId} was replaced with it's value during release:perform
> --
[ http://jira.codehaus.org/browse/MRELEASE-114?page=comments#action_65622 ]
Paul Spencer commented on MRELEASE-114:
---
Fogot to set affected version to Release plugin 2.0-beta-4
> ${project.artifactId} was replaced with it's value during release:perform
