[
https://issues.apache.org/jira/browse/SCM-213?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17960407#comment-17960407
]
ASF GitHub Bot commented on SCM-213:
------------------------------------
jira-importer commented on issue #396:
URL: https://github.com/apache/maven-scm/issues/396#issuecomment-2964591648
**[Joerg
Schaible](https://issues.apache.org/jira/secure/ViewProfile.jspa?name=joehni)**
commented
I've been running Cygwin & Maven 1/2 for years in combination with the
Windows versions of CVS/Subversion without any problem. The provided outputs
above show clearly, that in all cases a DOS path was provided to a Cygwin
compiled utility.
What was ??derogating?? about the comment? If one ever manages to build a
complete VM on top of Cygwin (SableVM/Classpath or Harmony might once be
available), those will automagically understand and use the paths of the
underlaying system => Cygwin. Maven works happily on other POSIX file systems,
because the VM provides the appropriate functionality (e.g. called indirectly
by File.getAbsolutePath()).
> 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)
