[
https://jira.codehaus.org/browse/SCM-696?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=319699#comment-319699
]
Raúl Wegmann commented on SCM-696:
----------------------------------
Version 1.8.1 fixes the problem for us. We had to add the following section to
our parent POM in order to force the maven-release-plugin to use version 1.8.1,
because version 2.4 still depends on version 1.8:
{code}
<pluginManagement>
<plugin>
<artifactId>maven-release-plugin</artifactId>
<version>2.4</version>
<dependencies>
<dependency>
<groupId>org.apache.maven.scm</groupId>
<artifactId>maven-scm-provider-svnexe</artifactId>
<version>1.8.1</version>
</dependency>
</dependencies>
<configuration>
<useReleaseProfile>false</useReleaseProfile>
</configuration>
</plugin>
</pluginManagement>
{code}
> 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
