maven-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Wladimir Kopilevich (JIRA)" <>
Subject [jira] Commented: (MRELEASE-83) Wrong username during release:prepare tagging
Date Sat, 11 Aug 2007 01:32:13 GMT


Wladimir Kopilevich commented on MRELEASE-83:

I had the same problem and found out, that during cvs checkin the class org.apache.maven.scm.provider.cvslib.cvsjava.util.CvsConnection
loads the CVSROOT from "CVS\Root" relative to the local working directory. The file gets created
by the initial cvs checkout of the project.

In my case i checked out the project "abc" initially with user "a" so abc\CVS\Root contained
something like ":pserver:a@server:...." but i had user b configured in <connection/>.
The first check of modified files by release:prepare is made with user "b" but the check-in
uses "a".

Do anybody know whether this behaviour is intended and why?

> Wrong username during release:prepare tagging
> ---------------------------------------------
>                 Key: MRELEASE-83
>                 URL:
>             Project: Maven 2.x Release Plugin
>          Issue Type: Bug
>          Components: scm
>            Reporter: Niclas Hedhman
>             Fix For: 2.0-beta-7
> If I my Svn repository requires a different username than the login name, and I issue

>    mvn release:prepare
> The first phase (checking in modified POMs) will succeed with that username.
> Then somewhere between that point and writing out the file, the user
name falls back to the login name (in my case "niclas"), which is written into the
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
> Before starting the release:prepare, create a file manually which
> and everything will work.

This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators:
For more information on JIRA, see:


View raw message