[
https://jira.codehaus.org/browse/SCM-419?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Robert Scholte updated SCM-419:
-------------------------------
Description:
I am building from a branch of a project with the SCM URL defined as
{code:xml}
<connection>svn+ssh://localhost/example/svn/services/tag-test/branches/1.0.0</connection>
{code}
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:
{noformat}
[INFO] ------------------------------------------------------------------------
[ERROR] BUILD FAILURE
[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
{noformat}
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) :
{noformat}
svn copy svn+ssh://localhost/example/...
svn+ssh://MY_USERNAME@localhost/example/...
svn: Source and dest appear not to be in the same repository (....
{noformat}
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.
was:
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] ------------------------------------------------------------------------
[ERROR] BUILD FAILURE
[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.
> Maven Subversion provider get confused by -Dusername= parameter when doing a
> release:prepare (Tagging operation)
> ----------------------------------------------------------------------------------------------------------------
>
> Key: SCM-419
> URL: https://jira.codehaus.org/browse/SCM-419
> 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
> {code:xml}
> <connection>svn+ssh://localhost/example/svn/services/tag-test/branches/1.0.0</connection>
> {code}
> 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:
> {noformat}
> [INFO]
> ------------------------------------------------------------------------
> [ERROR] BUILD FAILURE
> [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
> {noformat}
> 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) :
> {noformat}
> svn copy svn+ssh://localhost/example/...
> svn+ssh://MY_USERNAME@localhost/example/...
> svn: Source and dest appear not to be in the same repository (....
> {noformat}
> 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, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
