[ 
https://issues.apache.org/jira/browse/SCM-804?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Eric Pederson updated SCM-804:
------------------------------
    Description: As mentioned in SCM-213, the Maven release plugin breaks when 
using Cygwin's {{svn}}.  There is a workaround to use a Windows Subversion 
client instead.  Since the documentation lists {{useCygwinPath}} as an option 
it would be good if it worked everywhere.  I checked the source and 
{{useCygwinPath}} only appears to be used in the Update command.  Either the 
docs should clarify where it can be used or (ideally) it could be used for 
Commit and Checkout too.  (was: As mentioned in SCM-213, the Maven release 
plugin breaks when using Cygwin's {{svn}}.  There is a workaround to use a 
Windows Subversion client instead.  Since the documentation lists 
{{useCygwinPath}} as an option it would be good if it worked everywhere.  I 
checked the source and {{useCygwinPath}} only appears to be used in the Update 
command.  Either the docs should clarify where it can be used or (ideally) it 
could be used for commits too.)

> Expand SVN's useCygwinPath to all commands needed by release plugin
> -------------------------------------------------------------------
>
>                 Key: SCM-804
>                 URL: https://issues.apache.org/jira/browse/SCM-804
>             Project: Maven SCM
>          Issue Type: Improvement
>          Components: maven-scm-provider-svn
>            Reporter: Eric Pederson
>
> As mentioned in SCM-213, the Maven release plugin breaks when using Cygwin's 
> {{svn}}.  There is a workaround to use a Windows Subversion client instead.  
> Since the documentation lists {{useCygwinPath}} as an option it would be good 
> if it worked everywhere.  I checked the source and {{useCygwinPath}} only 
> appears to be used in the Update command.  Either the docs should clarify 
> where it can be used or (ideally) it could be used for Commit and Checkout 
> too.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Reply via email to