[ https://jira.codehaus.org/browse/SCM-696?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=319680#comment-319680 ]
Rafael Alcántara edited comment on SCM-696 at 2/14/13 8:35 AM: --------------------------------------------------------------- I am using release-plugin 2.4 and scm-plugin 1.8.1, but get this very same error: {noformat} [INFO] Tagging release with the label rhea-index-1.3.6... [INFO] Executing: /bin/sh -c cd /Users/rafa/projects/rhea/rhea-index && svn --username ralcantara --no-auth-cache --non-interactive copy --file /var/folders/mp/sncwnzl94t7cd98md0l_yfk40000gs/T/maven-scm-1553602371.commit svn+ssh://svn.code.sf.net/p/rhea-ebi/code/trunk/rhea-index svn+ssh://ralcant...@svn.code.sf.net/p/rhea-ebi/code/tags/rhea-index-1.3.6 [INFO] Working directory: /Users/rafa/projects/rhea/rhea-index [INFO] ------------------------------------------------------------------------ [INFO] BUILD FAILURE [INFO] ------------------------------------------------------------------------ [INFO] Total time: 4.308s [INFO] Finished at: Thu Feb 14 13:49:58 GMT 2013 [INFO] Final Memory: 10M/81M [INFO] ------------------------------------------------------------------------ [ERROR] Failed to execute goal org.apache.maven.plugins:maven-release-plugin:2.4:prepare (default-cli) on project rhea-index: Unable to tag SCM [ERROR] Provider message: [ERROR] The svn tag command failed. [ERROR] Command output: [ERROR] svn: Source and dest appear not to be in the same repository (src: 'svn+ssh://svn.code.sf.net/p/rhea-ebi/code/trunk/rhea-index'; dst: 'svn+ssh://ralcant...@svn.code.sf.net/p/rhea-ebi/code/tags/rhea-index-1.3.6') {noformat} As you see I use the -Dusername mvn option, but the result is exactly the same if I don't (my username appears in the svn info). I have also added these two lines to my .ssh/config file, to no avail: {noformat} Host svn.code.sf.net User ralcantara {noformat} The error comes obviously from svn. If I try to run the very same command, I get the very same error: {noformat} svn cp svn+ssh://svn.code.sf.net/p/rhea-ebi/code/trunk/rhea-index svn+ssh://ralcant...@svn.code.sf.net/p/rhea-ebi/code/tags/rhea-index-1.3.6 svn: Source and dest appear not to be in the same repository (src: 'svn+ssh://svn.code.sf.net/p/rhea-ebi/code/trunk/rhea-index'; dst: 'svn+ssh://ralcant...@svn.code.sf.net/p/rhea-ebi/code/tags/rhea-index-1.3.6') {noformat} However, just removing my username makes it work like a charm: {noformat} svn cp svn+ssh://svn.code.sf.net/p/rhea-ebi/code/trunk/rhea-index svn+ssh://svn.code.sf.net/p/rhea-ebi/code/tags/rhea-index-1.3.6 -m 'rhea-index-1.3.6' Committed revision 3060. {noformat} , and also adding my username to both URLs: {noformat} svn cp svn+ssh://ralcant...@svn.code.sf.net/p/rhea-ebi/code/trunk/rhea-index svn+ssh://ralcant...@svn.code.sf.net/p/rhea-ebi/code/tags/rhea-index-dltm -m DeleteMe Committed revision 3061. {noformat} As I said, the remote username already appears in my svn info: {noformat} svn info Path: . URL: svn+ssh://ralcant...@svn.code.sf.net/p/rhea-ebi/code/trunk/rhea-index Repository Root: svn+ssh://ralcant...@svn.code.sf.net/p/rhea-ebi/code {noformat} Can we make maven-scm-plugin smarter so that it adds the username to the URL while tagging? Thanks! was (Author: ralcantara): I am using release-plugin 2.4 and scm-plugin 1.8.1, but get this very same error: {noformat} [INFO] Tagging release with the label rhea-index-1.3.6... [INFO] Executing: /bin/sh -c cd /Users/rafa/projects/rhea/rhea-index && svn --username ralcantara --no-auth-cache --non-interactive copy --file /var/folders/mp/sncwnzl94t7cd98md0l_yfk40000gs/T/maven-scm-1553602371.commit svn+ssh://svn.code.sf.net/p/rhea-ebi/code/trunk/rhea-index svn+ssh://ralcant...@svn.code.sf.net/p/rhea-ebi/code/tags/rhea-index-1.3.6 [INFO] Working directory: /Users/rafa/projects/rhea/rhea-index [INFO] ------------------------------------------------------------------------ [INFO] BUILD FAILURE [INFO] ------------------------------------------------------------------------ [INFO] Total time: 4.308s [INFO] Finished at: Thu Feb 14 13:49:58 GMT 2013 [INFO] Final Memory: 10M/81M [INFO] ------------------------------------------------------------------------ [ERROR] Failed to execute goal org.apache.maven.plugins:maven-release-plugin:2.4:prepare (default-cli) on project rhea-index: Unable to tag SCM [ERROR] Provider message: [ERROR] The svn tag command failed. [ERROR] Command output: [ERROR] svn: Source and dest appear not to be in the same repository (src: 'svn+ssh://svn.code.sf.net/p/rhea-ebi/code/trunk/rhea-index'; dst: 'svn+ssh://ralcant...@svn.code.sf.net/p/rhea-ebi/code/tags/rhea-index-1.3.6') {noformat} As you see I use the -Dusername mvn option, but the result is the same if I don't. I have also added these two lines to my .ssh/config file, to no avail: {noformat} Host svn.code.sf.net User ralcantara {noformat} > SVN tagging fails with svn+ssh://username@host URL > -------------------------------------------------- > > Key: SCM-696 > URL: https://jira.codehaus.org/browse/SCM-696 > Project: Maven SCM > Issue Type: Bug > Components: maven-scm-provider-svn > Affects Versions: 1.8 > Reporter: Raúl Wegmann > Assignee: Olivier Lamy > Fix For: 1.8.1 > > Attachments: maven-scm-provider-svnexe.diff > > > Using the release plugin 2.3.2, the following error occurs when using a > svn+ssh://username@host URL: > {code} > [ERROR] Failed to execute goal > org.apache.maven.plugins:maven-release-plugin:2.3.2:prepare (default-cli) on > project project: Unable to tag SCM > [ERROR] Provider message: > [ERROR] The svn tag command failed. > [ERROR] Command output: > [ERROR] svn: Source and dest appear not to be in the same repository (src: > 'svn+ssh://svn.example.com/svn/project/trunk'; dst: > 'svn+ssh://usern...@svn.intranet.qrr.es/svn.example.com/svn/project/tags/tag-name-1.0') > {code} > I think I narrowed the cause down to the SvnTagCommand class of the > maven-scm-provider-svnexe module. Applying the attached patch the release > works without a problem. > A fix for a similar problem was reported and fixed by SCM-217, but changes of > SCM-262 did not consider this case. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://jira.codehaus.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira