[
http://jira.codehaus.org/browse/SCM-213?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=154793#action_154793
]
Andy Schlaikjer commented on SCM-213:
-------------------------------------
I still have this problem when using cygwin svn. Looking at the Maven SCM
support page for Subversion [1], it still doesn't look like any
path-to-svn-binary configuration is available. The code in [2] would likely
need to be updated to use some configured path instead of the simple "svn"
binary name.
[1] http://maven.apache.org/scm/subversion.html
[2]
https://svn.apache.org/repos/asf/maven/scm/tags/maven-scm-1.1/maven-scm-providers/maven-scm-providers-svn/maven-scm-provider-svnexe/src/main/java/org/apache/maven/scm/provider/svn/svnexe/command/SvnCommandLineUtils.java
> Broken with Cygwin
> ------------------
>
> Key: SCM-213
> URL: http://jira.codehaus.org/browse/SCM-213
> Project: Maven SCM
> 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
> 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 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
