[
https://jira.codehaus.org/browse/MRELEASE-146?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=337593#comment-337593
]
Andreas Höhmann edited comment on MRELEASE-146 at 12/17/13 4:31 AM:
--------------------------------------------------------------------
Please reopen this bug. I'm using version 2.4.2. and still have this problem.
I tried
C:\Users\hoehmann\.scm\svn-settings.xml
I tried
/home/hoehmann/.scm/svn-settings.xml
<svn-settings>
<useCygwinPath>true</useCygwinPath>
<cygwinMountPath>/cygwin</cygwinMountPath>
</svn-settings>
mvn release:prepare crash with
[ERROR] Failed to execute goal
org.apache.maven.plugins:maven-release-plugin:2.4.2:prepare (default-cli) on
project goos-tools: Unable to commit files
[ERROR] Provider message:
[ERROR] The svn command failed.
[ERROR] Command output:
[ERROR] svn: E155010: Commit failed (details follow):
[ERROR] svn: E155010: The node
'/cygdrive/d/DEV/ws_hscm/goos-tools/D:/DEV/ws_hscm' was not found.
[ERROR] -> [Help 1]
was (Author: ahoehma):
Please reopen this bug. I'm using version 2.4.2. and still have this
problem.
I tried
C:\Users\hoehmann\.scm\svn-settings.xml
I tried
/home/hoehmann/.scm/svn-settings.xml
mvn release:prepare crash with
[ERROR] Failed to execute goal
org.apache.maven.plugins:maven-release-plugin:2.4.2:prepare (default-cli) on
project goos-tools: Unable to commit files
[ERROR] Provider message:
[ERROR] The svn command failed.
[ERROR] Command output:
[ERROR] svn: E155010: Commit failed (details follow):
[ERROR] svn: E155010: The node
'/cygdrive/d/DEV/ws_hscm/goos-tools/D:/DEV/ws_hscm' was not found.
[ERROR] -> [Help 1]
> Release tag with SVN under Cygwin fails when sending the svn command a bad
> absolute path
> ----------------------------------------------------------------------------------------
>
> Key: MRELEASE-146
> URL: https://jira.codehaus.org/browse/MRELEASE-146
> Project: Maven Release Plugin
> Issue Type: Bug
> Components: scm
> Affects Versions: 2.0-beta-4
> Environment: Windows XP
> Reporter: Christian Gruber
>
> When release:prepare is invoked, on a cygwin system using svn provided with
> cygwin, the following error occurs.
> [INFO] Checking in modified POMs...
> [INFO] Executing: svn --non-interactive commit --file
> E:\DOCUME~1\CGRUBE~1.DJI\LOCALS~1\Temp\maven-scm-1141263545.commit
> E:/projects/israfil-fw/net.israfil.foundation-JDK1.4/pom.xml
> [INFO] Working directory: E:\projects\israfil-fw\net.israfil.foundation-JDK1.4
> [INFO]
> ------------------------------------------------------------------------
> [ERROR] BUILD FAILURE
> [INFO]
> ------------------------------------------------------------------------
> [INFO] Unable to commit files
> Provider message:
> The svn command failed.
> Command output:
> svn:
> '/projects/israfil-fw/net.israfil.foundation-JDK1.4/E:/projects/israfil-fw/net.israfil.foundation-JDK1.4'
> is not a working copy
> ...
> SVN on cygwin interprets
> E:/projects/israfil-fw/net.israfil.foundation-JDK1.4/pom.xml to be
> /projects/israfil-fw/net.israfil.foundation-JDK1.4/E:/projects/israfil-fw/net.israfil.foundation-JDK1.4,
> essentially appending the absolute path on the current working driectory as
> if it were a relative path.
> This is very odd, since "svn <command>
> E:/projects/israfil-fw/net.israfil.foundation-JDK1.4" works like a charm. I
> tried it with E: and e: to no avail.
> Proposed solution: Use relative paths
> Alternative - really really bad alternative: detect the presence of cygwin
> and re-structure the file path to use /cygdrive/e/blah/blah format.
> Ultimate remedy: Figure out why SVN is interpreting this way and fix in svn.
> -Christian.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
