Wrong username during release:prepare tagging

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.

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?

we need to push a release of beta-7 to do a release of 2.0.8. Bumping to next release

Same problem with 2.0-beta-8 and SVN.

I looked into DefaultScmRepositoryConfigurator: the username is contained in the host part of the ScmProviderRepositoryWithHost, but it's never extracted from that and scmRepo.setUser( username ) is never called with that value.

So I changed that and wrote some code to extract the username and password from the SVN URL. Now the username is set. Therefore, in ScmCommitPhase.checkin(...) the following code is called

result = provider.checkIn( repository, fileSet, (ScmVersion) null, message );

with a configured username:

• in the provider's username attribute
• the URL
• and the host name

but still I'm being asked for the wrong username! What is going on after that? I mean: it's a direct call on the ScmProvider. A problem with the SVN provider implementation?!?

Another workaround is to specify your remote username in a <server> section in settings.xml.

I have something like this in mine:

<settings>
  <servers>
    ...
   <server>
      <username>dennisl</username>
      <id>apache.releases</id>
      ...
    </server>
    ...
  </servers>
  ...
</settings>

Moving to a later version.

The attached patch fixes this issue for me when using CVS (the all java cvs client)

I get the same result that the first Login and also the update cvs commands work, but the checkin and tag commands won't work. As others have commented before, it uses the username defined in the CVS/Root file. Debugging the code I found out that it always checks the CVS/Root file, but if there is a -d option that takes precedence.

-d cvs_root_directory
Use cvs_root_directory as the root directory pathname of the reposi-
tory. Overrides the setting of the $CVSROOT environment variable.
See `Repository' in the CVS manual.

A change in revision 518698 changed the behaviour to not include the -d option when generating the tag, checkin, update and branch cvs commands. The comment for that revision indicates that this was a problem for the update command. I think that maybe it should have only be changed for the update command while leaving the tag and checkin behaviour to include the -d option.

See the comment for rev 518698 below:

Revision: 518698
Author: evenisse
Date: 3/15/07 6:17 PM
Comment:
Remove cvsroot from the command when it isn't needed. It fix some pb with update when files are updated only on the root directory and not detected.

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.