maven-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Andy Schlaikjer (JIRA)" <>
Subject [jira] Commented: (SCM-213) Broken with Cygwin
Date Thu, 20 Nov 2008 08:20:41 GMT


Andy Schlaikjer commented on SCM-213:

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:
>             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:
For more information on JIRA, see:


View raw message