[
https://issues.apache.org/jira/browse/SCM-804?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17963189#comment-17963189
]
ASF GitHub Bot commented on SCM-804:
------------------------------------
jira-importer commented on issue #1035:
URL: https://github.com/apache/maven-scm/issues/1035#issuecomment-2964640192
**[Eric
Pederson](https://issues.apache.org/jira/secure/ViewProfile.jspa?name=ericacm)**
commented
I’m at another job now and that doesn’t use maven. You can close this.
Thanks.
On Sat, Mar 10, 2018 at 6:26 PM Michael Osipov (JIRA) <[email protected]>
--
Sent from Gmail Mobile
> 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 (Moved to GitHub Issues)
> Issue Type: Improvement
> Components: maven-scm-provider-svn
> Reporter: Eric Pederson
> Priority: Minor
>
> 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
(v8.20.10#820010)
