Caused by: org.apache.maven.plugin.MojoExecutionException: Cant canonicalize system path: {0} at org.apache.maven.plugin.ide.IdeUtils.getCanonicalPath(IdeUtils.java:147) at org.apache.maven.plugin.ide.IdeUtils.toRelativeAndFixSeparator(IdeUtils.java:591) at org.apache.maven.plugin.eclipse.EclipsePlugin.extractResourceDirs(EclipsePlugin.java:1787)

If it was something working before could be :

looks like some file is corrupted that has the path to a resource. just guessing - make a new workspace and restart IDE with clean - and then try? Later you can root cause it.

Ref

http://stackoverflow.com/questions/11768106/clean-out-eclipse-workspace-metadata
http://stackoverflow.com/questions/4386119/eclipse-getting-too-slow-workspace-recreation-helped
http://stackoverflow.com/questions/2030064/how-to-run-eclipse-in-clean-mode-and-what-happens-if-we-do-so

 * Edit the |eclipse.ini| file located in your Eclipse install
   directory and insert |-clean| as the first line.
 * Or edit the shortcut you use to start Eclipse and add |-clean| as
   the first argument.
 * Or create a batch or shell script that calls the Eclipse executable
   with the |-clean| argument. The advantage to this step is you can
   keep the script around and use it each time you want to clean out
   the workspace. You can name it something like |eclipse-clean.bat|
   (or |eclipse-clean.sh|).

---





On 4/1/2013 7:27 PM, Ralph Goers wrote:
I'm not even sure what it is complaining about.

Sent from my iPad

On Apr 1, 2013, at 6:43 AM, Gary Gregory <garydgreg...@gmail.com <mailto:garydgreg...@gmail.com>> wrote:

Hi:

With the latest from trunk, running 'mvn eclipse:eclipse -X' I get:

[INFO] ------------------------------------------------------------------------
[INFO] Reactor Summary:
[INFO]
[INFO] Apache Log4j 2 .................................... SUCCESS [1.897s] [INFO] Apache Log4j API .................................. SUCCESS [0.395s] [INFO] Apache Log4J Core ................................. SUCCESS [0.745s] [INFO] Apache Log4j 1.x Compatibility API ................ SUCCESS [0.439s] [INFO] Apache Log4j SLF4J Binding ........................ SUCCESS [0.445s] [INFO] Apache Log4j to SLF4J Adapter ..................... SUCCESS [0.376s] [INFO] Apache Log4j Commons Logging Bridge ............... SUCCESS [0.421s] [INFO] Apache Log4j Flume NG Bridge ...................... SUCCESS [2.322s] [INFO] Log4j Web Adapters ................................ SUCCESS [0.407s] [INFO] log4j-samples ..................................... SUCCESS [0.260s] [INFO] flume-common ...................................... SUCCESS [0.777s] [INFO] flume-remote ...................................... FAILURE [1.485s]
[INFO] flume-embedded .................................... SKIPPED
[INFO] Apache Log4j Async ................................ SKIPPED
[INFO] ------------------------------------------------------------------------
[INFO] BUILD FAILURE
[INFO] ------------------------------------------------------------------------
[INFO] Total time: 12.110s
[INFO] Finished at: Mon Apr 01 09:40:22 EDT 2013
[INFO] Final Memory: 27M/335M
[INFO] ------------------------------------------------------------------------ [ERROR] Failed to execute goal org.apache.maven.plugins:maven-eclipse-plugin:2.9:eclipse (default-cli) on project flume-remote: Cant canonicalize system path: {0}: The filename, directory name, or volume label syntax is incorrect
-> [Help 1]
org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute goal org.apache.maven.plugins:maven-eclipse-plugin:2.9:eclipse (default-cli) on project flume-remote: Cant canonicalize system path: {0} at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:217) at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:153) at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:145) at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:84) at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:59) at org.apache.maven.lifecycle.internal.LifecycleStarter.singleThreadedBuild(LifecycleStarter.java:183) at org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:161)
        at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:320)
        at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:156)
        at org.apache.maven.cli.MavenCli.execute(MavenCli.java:537)
        at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:196)
        at org.apache.maven.cli.MavenCli.main(MavenCli.java:141)
        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.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:290) at org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:230) at org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:409) at org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:352) Caused by: org.apache.maven.plugin.MojoExecutionException: Cant canonicalize system path: {0} at org.apache.maven.plugin.ide.IdeUtils.getCanonicalPath(IdeUtils.java:147) at org.apache.maven.plugin.ide.IdeUtils.toRelativeAndFixSeparator(IdeUtils.java:591) at org.apache.maven.plugin.eclipse.EclipsePlugin.extractResourceDirs(EclipsePlugin.java:1787) at org.apache.maven.plugin.eclipse.EclipsePlugin.buildDirectoryList(EclipsePlugin.java:1676) at org.apache.maven.plugin.eclipse.EclipsePlugin.createEclipseWriterConfig(EclipsePlugin.java:1359) at org.apache.maven.plugin.eclipse.EclipsePlugin.writeConfiguration(EclipsePlugin.java:1178) at org.apache.maven.plugin.ide.AbstractIdeSupportMojo.execute(AbstractIdeSupportMojo.java:511) at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:101) at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:209)
        ... 19 more
Caused by: java.io.IOException: The filename, directory name, or volume label syntax is incorrect
        at java.io.WinNTFileSystem.canonicalize0(Native Method)
        at java.io.Win32FileSystem.canonicalize(Win32FileSystem.java:396)
        at java.io.File.getCanonicalPath(File.java:559)
at org.apache.maven.plugin.ide.IdeUtils.getCanonicalPath(IdeUtils.java:143)
        ... 27 more
[ERROR]
[ERROR]
[ERROR] For more information about the errors and possible solutions, please read the following articles: [ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/MojoExecutionException
[ERROR]
[ERROR] After correcting the problems, you can resume the build with the command
[ERROR]   mvn <goals> -rf :flume-remote

Thoughts?

--
E-Mail: garydgreg...@gmail.com <mailto:garydgreg...@gmail.com> | ggreg...@apache.org <mailto:ggreg...@apache.org>
JUnit in Action, 2nd Ed: http://bit.ly/ECvg0
Spring Batch in Action: http://bit.ly/bqpbCK
Blog: http://garygregory.wordpress.com <http://garygregory.wordpress.com/>
Home: http://garygregory.com/
Tweet! http://twitter.com/GaryGregory



Reply via email to