Details
-
Type:
Bug
-
Status:
Open
-
Priority:
Major
-
Resolution: Unresolved
-
Affects Version/s: None
-
Fix Version/s: None
-
Component/s: scm
-
Labels:None
-
Patch Submitted:Yes
-
Number of attachments :
Description
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.
Activity
| Field | Original Value | New Value |
|---|---|---|
| Project | maven-release-plugin [ 10346 ] | Maven 2.x Release Plugin [ 11144 ] |
| Workflow | jira [ 50467 ] | Maven [ 50472 ] |
| Key | MPRELEASE-18 | MRELEASE-83 |
| Workflow | Maven [ 50472 ] | Maven New [ 52258 ] |
| Fix Version/s | 2.0-beta-4 [ 12367 ] |
| Fix Version/s | 2.0 [ 12571 ] | |
| Fix Version/s | 2.0-beta-4 [ 12367 ] |
| Fix Version/s | 2.0 [ 12571 ] |
| Component/s | scm [ 12698 ] |
| Fix Version/s | 2.0-beta-7 [ 13560 ] |
| Fix Version/s | 2.0-beta-8 [ 13812 ] | |
| Fix Version/s | 2.0-beta-7 [ 13560 ] |
| Fix Version/s | 2.0-beta-8 [ 13812 ] | |
| Fix Version/s | 2.0-beta-9 [ 14682 ] |
| Fix Version/s | 2.0-beta-9 [ 14682 ] | |
| Fix Version/s | 2.0-beta-10 [ 15113 ] |
| Fix Version/s | 2.0 [ 15113 ] |
| Attachment | AbstractCvsCheckInCommand.java.patch [ 48496 ] |
| Patch Submitted | [Yes] |