[
https://issues.apache.org/jira/browse/SCM-213?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17960413#comment-17960413
]
ASF GitHub Bot commented on SCM-213:
------------------------------------
jira-importer commented on issue #396:
URL: https://github.com/apache/maven-scm/issues/396#issuecomment-2964591665
**[Andy
Schlaikjer](https://issues.apache.org/jira/secure/ViewProfile.jspa?name=hazen)**
commented
Olivier, of course. The problem does not exhibit itself when windows svn is
default in path. However, despite Emmanuel's comment, this issue is not
resolved in the case of cygwin svn. I thought that Christian's suggestion of a
method to configure path to svn binary used by maven-release-plugin eminently
reasonable, but noticed it had not yet been acted upon.
> Broken with Cygwin
> ------------------
>
> Key: SCM-213
> URL: https://issues.apache.org/jira/browse/SCM-213
> Project: Maven SCM (Moved to GitHub Issues)
> Issue Type: Bug
> Components: maven-scm-provider-svn
> Affects Versions: 1.0-beta-3
> Environment: Cygwin under Windows, Maven release plugin version
> 2.0-beta-4
> Reporter: Chas Douglass
> Assignee: Emmanuel Venisse
> Priority: Major
> Fix For: 1.0-rc1
>
>
> svn doesn't like absolute path for the files to commit when we run it under
> cygwin with a windows svn and a cygwin svn.
> svn --non-interactive commit --file c:\temp\maven-scm-945043858.commit
> e:/newapps/JEC/pom.xml
> Working directory: e:\newapps\JEC
> doesn't works with the same error you have
> svn --non-interactive commit --file c:\temp\maven-scm-945043858.commit pom.xml
> Working directory: e:\newapps\JEC
> works fine.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
