[
http://jira.codehaus.org/browse/MRELEASE-83?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_100668
]
Jaran Nilsen commented on MRELEASE-83:
--------------------------------------
Having the same issue with 2.0-beta-6. The first checkout the plugin performs
works fine, but when the modified POM is to be checked in, the plugin uses the
username of the logged on user on the computer, instead of what's specified in
the scm.connection/developerConnection in the POM. The -Dusername= parameter,
or the workaround proposed by Niclas is not working in 2.0-beta-6 as far as I
can see.
> 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
>
> If I my Svn repository requires a different username than the login name, and
> I issue
> mvn [EMAIL PROTECTED] 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
> [EMAIL PROTECTED]
> 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
