[
http://jira.codehaus.org/browse/MRELEASE-83?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=235322#action_235322
]
Brett Porter commented on MRELEASE-83:
--------------------------------------
this needs a closer review, since the original reporter had issues with SVN,
and the patch only covers CVS. It also indicates there's an SCM component to be
fixed, which isn't in scope for the next release plugin release now that 1.4 is
already out.
> Wrong username during release:prepare tagging
> ---------------------------------------------
>
> Key: MRELEASE-83
> URL: http://jira.codehaus.org/browse/MRELEASE-83
> Project: Maven 2.x Release Plugin
> Issue Type: Bug
> Components: scm
> Reporter: Niclas Hedhman
> Attachments: AbstractCvsCheckInCommand.java.patch
>
>
> If I my Svn repository requires a different username than the login name, and
> I issue
> mvn -dmaven.username=nic...@hedhman.org release:prepare
> The first phase (checking in modified POMs) will succeed with that username.
> Then somewhere between that point and writing out the release.properties
> file, the user name falls back to the login name (in my case "niclas"), which
> is written into the release.properties file, and used during the tagging of
> the repository.
> Now, looking at the source, I think that is unwise to keep a username both in
> the ReleaseProgressTracker as well as in the ScmHelper, and I suspect that
> there is some type of sequencing problem in there.
> WORKAROUND;
> Before starting the release:prepare, create a release.properties file
> manually which contains
> maven.username=nic...@hedhman.org
> and everything will work.
--
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
