edgarosy wrote: > > Question for all maven gurus. Hope you can help me.. > > I've been using a maven-release plugin for over a year and it has always > work perfectly when creating new branch from source (trunk). Ever since > our SVN amdin upgraded the SVN server to use version 1.6 instead of 1.4 I > have not been able to commit files to svn successfully after the branch > has been created. > > my build servers is a windows 2003 server. I am using Maven version: > 2.2.1, and I upgraded the svn client to 1.6.1. > > > > [INFO] Executing: cmd.exe /X /C "svn --username xxxx.xxxx --password ***** > --non-interactive commit --file "C:\Documents and > Settings\triacp\maven-scm-528237796.commit" --targets "C:\Documents and > Settings\triacp\maven-scm-1457486069711445316-targets"" > [INFO] Working directory: D:\build\buildScripts\mvnScripts\branching > org.apache.maven.shared.release.scm.ReleaseScmCommandException: Unable to > commit files > Provider message: > The svn command failed. > Command output: > cygwin warning: > MS-DOS style path detected: C:\Documents and > Settings\triacp\maven-scm-528237796.commit > Preferred POSIX equivalent is: /cygdrive/c/Documents and > Settings/triacp/maven-scm-528237796.commit > CYGWIN environment variable option "nodosfilewarning" turns off this > warning. > Consult the user's guide for more details about POSIX paths: > http://cygwin.com/cygwin-ug-net/using.html#using-pathnames > svn: > '/cygdrive/d/build/buildScripts/mvnScripts/branching/D:/build/buildScripts/mvnScripts/branching' > is not a working copy > svn: > '/cygdrive/d/build/buildScripts/mvnScripts/branching/D:/build/buildScripts/mvnScripts/branching' > does not exist
Don't use the Cygwin version of the svn client. The JVM is a Windows app and can therefore never provide proper paths for a Cygwin-based svn client. Since the Windows svn client will use CRLF as native EOL, you should also use this svn only on text-mountet directories, so that Cygwin-based utilities use the same EOL. - Jörg --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
