You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@maven.apache.org by edgarosy <ed...@gmail.com> on 2010/11/22 22:00:36 UTC

Unable to commit files to SVN after new branch has been created with the maven-release plugin

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

        at
org.apache.maven.shared.release.phase.ScmCommitPhase.checkin(ScmCommitPhase.java:133)
        at
org.apache.maven.shared.release.phase.ScmCommitPhase.execute(ScmCommitPhase.java:109)
        at
org.apache.maven.shared.release.DefaultReleaseManager.branch(DefaultReleaseManager.java:379)
        at
org.apache.maven.shared.release.DefaultReleaseManager.branch(DefaultReleaseManager.java:350)
        at
org.apache.maven.plugins.release.BranchReleaseMojo.execute(BranchReleaseMojo.java:133)
        at
org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:490)
        at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:694)
        at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeStandaloneGoal(DefaultLifecycleExecutor.java:569)
        at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:539)
        at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:387)
        at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:284)
        at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:180)
        at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:328)
        at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:138)
        at org.apache.maven.cli.MavenCli.main(MavenCli.java:362)
        at
org.apache.maven.cli.compat.CompatibleMain.main(CompatibleMain.java:60)
        at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
        at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
        at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
        at java.lang.reflect.Method.invoke(Method.java:597)
        at
org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315)
        at org.codehaus.classworlds.Launcher.launch(Launcher.java:255)
        at
org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430)
        at org.codehaus.classworlds.Launcher.main(Launcher.java:375)
[INFO]
------------------------------------------------------------------------
[ERROR] BUILD FAILURE
[INFO]
------------------------------------------------------------------------
[INFO] 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

[INFO]
------------------------------------------------------------------------
[INFO] For more information, run Maven with the -e switch
[INFO]
------------------------------------------------------------------------
[INFO] Total time: 11 minutes 49 seconds
[INFO] Finished at: Mon Nov 22 11:17:26 MST 2010
[INFO] Final Memory: 32M/77M
[INFO]
------------------------------------------------------------------------

-- 
View this message in context: http://maven.40175.n5.nabble.com/Unable-to-commit-files-to-SVN-after-new-branch-has-been-created-with-the-maven-release-plugin-tp3276023p3276023.html
Sent from the Maven - Users mailing list archive at Nabble.com.

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org

Re: Unable to commit files to SVN after new branch has been created with the maven-release plugin

Posted by Jörg Schaible <jo...@gmx.de>.
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: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org

Re: Unable to commit files to SVN after new branch has been created with the maven-release plugin

Posted by Wayne Fay <wa...@gmail.com>.
> 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

Probably your problem is related to these lines... I doubt that path
is right (.../d/build/.../D:/build/...).

Wayne

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org

Re: Unable to commit files to SVN after new branch has been created with the maven-release plugin

Posted by Kalle Korhonen <ka...@gmail.com>.
Use regular command prompt, not cygwin when making a release. (If you
find a better fix, let me know.)

Kalle


On Mon, Nov 22, 2010 at 1:00 PM, edgarosy <ed...@gmail.com> 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
>
>        at
> org.apache.maven.shared.release.phase.ScmCommitPhase.checkin(ScmCommitPhase.java:133)
>        at
> org.apache.maven.shared.release.phase.ScmCommitPhase.execute(ScmCommitPhase.java:109)
>        at
> org.apache.maven.shared.release.DefaultReleaseManager.branch(DefaultReleaseManager.java:379)
>        at
> org.apache.maven.shared.release.DefaultReleaseManager.branch(DefaultReleaseManager.java:350)
>        at
> org.apache.maven.plugins.release.BranchReleaseMojo.execute(BranchReleaseMojo.java:133)
>        at
> org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:490)
>        at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:694)
>        at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeStandaloneGoal(DefaultLifecycleExecutor.java:569)
>        at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:539)
>        at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:387)
>        at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:284)
>        at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:180)
>        at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:328)
>        at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:138)
>        at org.apache.maven.cli.MavenCli.main(MavenCli.java:362)
>        at
> org.apache.maven.cli.compat.CompatibleMain.main(CompatibleMain.java:60)
>        at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>        at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
>        at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
>        at java.lang.reflect.Method.invoke(Method.java:597)
>        at
> org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315)
>        at org.codehaus.classworlds.Launcher.launch(Launcher.java:255)
>        at
> org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430)
>        at org.codehaus.classworlds.Launcher.main(Launcher.java:375)
> [INFO]
> ------------------------------------------------------------------------
> [ERROR] BUILD FAILURE
> [INFO]
> ------------------------------------------------------------------------
> [INFO] 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
>
> [INFO]
> ------------------------------------------------------------------------
> [INFO] For more information, run Maven with the -e switch
> [INFO]
> ------------------------------------------------------------------------
> [INFO] Total time: 11 minutes 49 seconds
> [INFO] Finished at: Mon Nov 22 11:17:26 MST 2010
> [INFO] Final Memory: 32M/77M
> [INFO]
> ------------------------------------------------------------------------
>
> --
> View this message in context: http://maven.40175.n5.nabble.com/Unable-to-commit-files-to-SVN-after-new-branch-has-been-created-with-the-maven-release-plugin-tp3276023p3276023.html
> Sent from the Maven - Users mailing list archive at Nabble.com.
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> For additional commands, e-mail: users-help@maven.apache.org
>
>

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org