[ http://jira.codehaus.org/browse/SCM-213?page=comments#action_70630 ] erwin commented on SCM-213: ---------------------------
Same issue. The command output here is: Provider message: The svn command failed. Command output: svn: '/cygdrive/c/TomTom/tmp/release/myapp/c:/TomTom/tmp/release/myapp' is not a working copy svn doesn't see paths starting with c:/ as absolute. I think the previous version of the plugin must not have put the current working directory in from of the file names that are being committed, since things worked fine earlier. > 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 > Fix For: 1.0 > > > 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
