maven-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Kristoffer Moum (JIRA)" <>
Subject [jira] Commented: (SCM-419) Maven Subversion provider get confused by -Dusername= parameter when doing a release:prepare (Tagging operation)
Date Tue, 14 Apr 2009 14:27:54 GMT


Kristoffer Moum commented on SCM-419:

I have the exact same problem. However, I found a workaround as it only plays tricks on me
if I specifically state -Dusername. Rather than specifying a username from the command line,
I added the following to ~/.ssh/config:

User username

(Remember an empty line after username.)

This way, I don't have to specify the username from the command-line and it is not appended
to the scm string for any commands.

> Maven Subversion provider get confused by -Dusername= parameter when doing a release:prepare
(Tagging operation)
> ----------------------------------------------------------------------------------------------------------------
>                 Key: SCM-419
>                 URL:
>             Project: Maven SCM
>          Issue Type: Bug
>          Components: maven-scm-provider-svn
>    Affects Versions: 2.0
>         Environment: Maven 2.0.9
> Mac OSX
> JDK 1.5.0_13-119
> Using svn+ssh with private/public key authentication
>            Reporter: David Trott
> I am building from a branch of a project with the SCM URL  defined  as
> <connection>svn+ssh://localhost/example/svn/services/tag-test/branches/1.0.0</connection>
> I have not defined <developerConnection>
> If I do not pass the -Dusername= parameter
> I can successfully do:
> - mvn release:prepare
> - mvn release:perform
> However if I set the -Dusername=MYUSERNAME to the same username as I am logged in as
the release:prepare step fails with:
> [INFO] ------------------------------------------------------------------------
> [INFO] ------------------------------------------------------------------------
> [INFO] Unable to tag SCM
> Provider message:
> The svn tag command failed.
> Command output:
> svn: Commit failed (details follow):
> svn: Source url 'svn+ssh://localhost/example/svn/services/tag-test/branches/1.0.0' is
from different repository
> Based on what is committed to svn this appears to be occurring when the release plugin
is trying to perform the tagging operation.
> NOTE: The command line version of svn (version 1.4.4) also gets confused when passed
two urls (one with and one without a username) :
> svn copy svn+ssh://localhost/example/... svn+ssh://MY_USERNAME@localhost/example/...
> svn: Source and dest appear not to be in the same repository (....
> Hence I suspect that in order to fix this issue it will be necessary to consider the
source of the copy when building the target URL for the tagging operation.

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