You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Dennis Lundberg (JIRA)" <ji...@codehaus.org> on 2010/01/18 19:21:56 UTC
[jira] Updated: (MRELEASE-83) Wrong username during release:prepare
tagging
[ http://jira.codehaus.org/browse/MRELEASE-83?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Dennis Lundberg updated MRELEASE-83:
------------------------------------
Fix Version/s: (was: 2.0)
Moving to a later version.
> 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 -Dmaven.username=niclas@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=niclas@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