maven release:prepare fails; seems to be confused about svn's UUID -
When I try to use the release release plugin, it fails on mvn release:
the following error:
I'm certain stores UUID Account 221b71b0-5d3c-7840-b153-25850b4df36e, and checkin tested and check out.
I have removed all local source code and checked it again, still this is the error.
I have confirmed that in the svn entries file, this refers to the correct UUID 221b71b0-5d3c-7840-b153-25850b4df36e.
I have run svnlook uuid e: \ repositories \ myrepo
and it gives 221b71b0-5d3c-7840-b153-25850b4df36e.
But in some way, Maven thinks that when it tries to tag it, the UUID is different.
I am able to make my own tag with SVN client. My SVN server is local on my machine, this view is running under SSVN Vista. I am able to check files in and out with Eclipse.
I am in my mind on this! The only thing I can think of is that the name of the local machine is different from the repository URL. I.e., I am using DynDNS to route traffic to repo.modeman.com, and it is installed in the routine of traffic for the proper service in my router. In other words, OS thinks my machine name is A_NAME, but I'm reaching svn via url repo.mydomain.com. Is it possible that Maven is confused because of this?
I do not know what to do between Maven and Visual SVN. help please!
Final Note: When I run with the ultimate -e to Maven, so I get this stack trace:
[INFO] Trace org.apache.maven.BuildFailureException: in Incomplete tag SCM Provider Message: svn tag command failed. Command output: SVN: stores UUID '3da89ab5-aa79-4544-a1de-ca02bd87a2ce' hope does not match Ed UUID '221b71b0-5d3c-7840-b153-25850b4df36e' on org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals (Defa org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeStandalone goal org.apache (DefaultLifecycleExecutor.java ts696) on algifecycleExecutor.java on org.apache on org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGuol (Defau ltLifecycleExecutor.java) 39) : 715) .maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHalan (default LifecycleExecutor.java:387) on org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegmen (DefaultLifecycleExecutor.java:284) on org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute (DefaultLi) at org.apache.maven.DefaultMaven.execute (DefaultMaven.java:180) org.apache.maven On .DefaultMaven.deExecute (DefaultMaven.java:328) phcycleExecutor.java:180) on org.apache.maven.cli.MavenCli.main org.apache.maven.cli.compat.CompatibleMain.main (MavenCli.java:362 ) (CompatibleMain.java:6 0) (Native method sun.reflect.NativeMethodAccessorImpl.invoke0) on sun.reflect.NativeMethodAccessorImpl.invoke (NativeMethodAccessorImpl. Java: 39) sun.reflect.DelegatingMethodAccessorImpl.invoke (DelegatingMethodAcces sorImpl.java:25) java.lang.reflect.Method.invoke (Method.java:597) on org.codehaus.classworlds.Launcher.launchEnhanced (launcher. Java: 315) org.codehaus.classworlds.Launcher.launch (Launcher.java:255) org.codehaus.classworlds.Launcher.mainWithExitCode (Launcher.java:430) at org.codehaus.classworlds.Launcher.main at (on Launcher Kjava: due by 375): org.apache.maven.plugin.MojoFailureException: SCM provider unable to message Tags: svn tag command failed command output: SVN: stores UUID '3da89ab5-aa79-4544-a1de-ca02bd87a2ce' Do not match the expectation at 'ad UUID org.apache.maven.plugins.release.PrepareReleaseMojo.execute' 221b71b0-5d3c-7840-b153-25850 On b4df36e 'org.apache.maven.plugin.DefaultPluginManager.executeMojo (PrepareRe leaseMojo.java:169) (DefaultPlugi nManager.java:490) on org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals (Defa ultLifecycleExecutor.java:694) ... 17 more
I feel like a numnut, but it tunrs know that when I get my SVN Repositories switching around, I neglected to update pom.xml, now all understand. But I would really like to have Maven's list of treasures it was using in production. This will save a full day of me hair pulling!
Comments
Post a Comment