[ http://jira.codehaus.org/browse/SCM-213?page=comments#action_71617 ] Christian Gruber commented on SCM-213: --------------------------------------
Even if they're windows apps, the SVN app is (in the above case) from Cygwin, and should understand c:/blah/foo as an absolute path. However, Joerg's right, it's not maven - the debug output shows the right path is passed, but for some reason, the conversion between windows/cygwin environments is causing cygwin to misinterpret the path as relative. The true fix is in the cygwin version of SVN. In the mean-time, this could be addressed by providing a configuration option to point to the svn binary, or the java SVN client from eclipse could be used, which would obviate the whole thing. As a short term fix, I recommend making the plugin configurable to point to an SVN binary, since trying to insert svn into a unix-like-path in cygwin makes for very brittle scripting. > 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
