[jira] Commented: (SCM-406) scm tag does not work with Subversion 1.5.1

["Kyle Lebel (JIRA)" <ji...@codehaus.org>]

    [ http://jira.codehaus.org/browse/SCM-406?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=153193#action_153193 ] 

Kyle Lebel commented on SCM-406:
--------------------------------

Hey guys, I downloaded the source code for the multiple dependencies (maven-release-plugin, maven-release-manager, maven-scm-providers-svn).  

If the maven-release-plugin you have is configured to use the latest, it will use 1.1 version of the maven-scm-providers.  Simply changing the following line 162 in SvnTagCommand resolves this issue:

cl.createArgument().setValue( "." ); 
  to
cl.createArgument().setValue( repository.getUrl() );

So not sure if someone would want to make an official revision for this.  For now I will deploy this to our local maven repository.  

> scm tag does not work with Subversion 1.5.1
> -------------------------------------------
>
>                 Key: SCM-406
>                 URL: http://jira.codehaus.org/browse/SCM-406
>             Project: Maven SCM
>          Issue Type: Bug
>          Components: maven-scm-provider-svn
>    Affects Versions: 1.0
>            Reporter: James William Dumay
>             Fix For: 1.1.1
>
>
> scm:checkin does not work with Subversion 1.5.1
> On release:perform (which I assume calls scm:checkin) the following error occurs:
> {code}
> svn: File '/svn/private/atlassian/confluence/tags/confluence-project-2.10-m1/conf-acceptance-test/pom.xml' already exists
> {code}
> Using subversion 1.4.x is a good enough workaround.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira