jira.codehaus.org

  • Log In Access more options
    • Online Help
    • Keyboard Shortcuts
    • About JIRA
    • JIRA Credits
    • What?s New
  • Dashboards Access more options (Alt+d)
  • Projects Access more options (Alt+p)
  • Issues Access more options (Alt+i)
  • Maven 2.x Eclipse Plugin
  • MECLIPSE-99

The plugin seems to append ${basedir} regardless of the nature of ${pom.build.output.directory}.

  • Log In
  • Views
    • XML
    • Word
    • Printable

Details

  • Type: Bug Bug
  • Status: Closed Closed
  • Priority: Major Major
  • Resolution: Won't Fix
  • Affects Version/s: 2.2
  • Fix Version/s: None
  • Component/s: None
  • Labels:
    None
  • Environment:
    Windows 2000 Professional,
    java -fullversion
    java full version "1.5.0_06-b05"

Description

The plugin seems to append ${basedir} regardless of the nature of ${pom.build.output.directory}.

In the following example my buildOutputDirectory is an absolute path
----------------
./mvn.bat -X eclipse:eclipse
.....
[DEBUG] Configuring mojo 'org.apache.maven.plugins:maven-eclipse-plugin:2.2:eclipse' -->
[DEBUG] (s) buildOutputDirectory = D:\stage\TMF814_1.0_DEV\sw\java\tmf814gw\classes
[DEBUG] (s) executedProject = org.apache.maven.project.MavenProject@ee459978
[DEBUG] (s) buildOutputDirectory = D:\stage\TMF814_1.0_DEV\sw\java\tmf814gw\classes
[DEBUG] (s) executedProject = org.apache.maven.project.MavenProject@ee459978
[DEBUG] (s) localRepository = [local] -> file://d:/stage/.maven/repository
[DEBUG] (s) project = org.apache.maven.project.MavenProject@ee459978
[DEBUG] (s) reactorProjects = [org.apache.maven.project.MavenProject@ee459978]
[DEBUG] (s) remoteArtifactRepositories = [[local] -> file:///D:/stage/.maven/repository, [vob] -> file://d:\jhb_sn_tmf814_view\axx_gw\java\Tmf814Gw/../lib/repository, [central] ->
n.org/maven2]
[DEBUG] (s) useProjectReferences = true
[DEBUG] (s) wtpversion = none
[DEBUG] – end configuration –
[INFO] [eclipse:eclipse]
[DEBUG] no.axxessit.gw.tmf814:tmf814gw:jar:1.0 (selected for null)
[WARNING] POM for 'axx:axxcommon:pom:3.0_maint:compile' is invalid. It will be ignored for artifact resolution. Reason: Not a v4.0.0 POM.
[DEBUG] Reason: Not a v4.0.0 POM.
[DEBUG] axx:axxcommon:jar:3.0_maint:compile (selected for compile)
[DEBUG] commons-collections:commons-collections:jar:3.1:compile (selected for compile)
[DEBUG] commons-logging:commons-logging:jar:1.0.4:compile (selected for compile)
[DEBUG] jacorb:jacorb:jar:2.2.3:compile (selected for compile)
[DEBUG] log4j:log4j:jar:1.2.8:compile (selected for compile) \res
[DEBUG] tmf:tmf814-idl:jar:2.1:compile (selected for compile)
[INFO] ------------------------------------------------------------------------
[ERROR] BUILD ERROR
[INFO] ------------------------------------------------------------------------
[INFO] Can't canonicalize system path: d:\jhb_sn_tmf814_view\axx_gw\java\Tmf814Gw\D:\stage\TMF814_1.0_DEV\sw\java\tmf814gw\classes\..\res

Embedded error: The filename, directory name, or volume label syntax is incorrect
[INFO] ------------------------------------------------------------------------
[DEBUG] Trace
org.apache.maven.lifecycle.LifecycleExecutionException: Can't canonicalize system path: d:\jhb_sn_tmf814_view\axx_gw\java\Tmf814Gw\D:\stage\TMF814_1.0_DEV\sw\java\tmf814gw\classes\..
at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:559)
at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeStandaloneGoal(DefaultLifecycleExecutor.java:488)
at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:458)
at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:306)
at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:273)
at org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:140)
at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:322)
at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:115) \..\res
at org.apache.maven.cli.MavenCli.main(MavenCli.java:256)
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:324)
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)
Caused by: org.apache.maven.plugin.MojoExecutionException: Can't canonicalize system path: d:\jhb_sn_tmf814_view\axx_gw\java\Tmf814Gw\D:\stage\TMF814_1.0_DEV\sw\java\tmf814gw\classes
at org.apache.maven.plugin.ide.IdeUtils.getCanonicalPath(IdeUtils.java:60)
at org.apache.maven.plugin.ide.IdeUtils.toRelativeAndFixSeparator(IdeUtils.java:72)
at org.apache.maven.plugin.eclipse.EclipsePlugin.extractResourceDirs(EclipsePlugin.java:720)
at org.apache.maven.plugin.eclipse.EclipsePlugin.buildDirectoryList(EclipsePlugin.java:614)
at org.apache.maven.plugin.eclipse.EclipsePlugin.writeConfiguration(EclipsePlugin.java:501)
at org.apache.maven.plugin.ide.AbstractIdeSupportMojo.execute(AbstractIdeSupportMojo.java:382)
at org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:412)

Issue Links

is related to

Bug - A problem which impairs or prevents the functions of the product. MNG-3747 relative build paths are not path-translated when using prefixed expressions (eg. project.build.directory) in plugin configurations

  • Major - Major loss of function.
  • Closed - The issue is considered finished, the resolution is correct. Issues which are not closed can be reopened.

Activity

Ascending order - Click to sort in descending order
  • All
  • Comments
  • Work Log
  • History
  • Activity
Hide
Permalink
Jan-Helge Bergesen added a comment - 26/Apr/06 7:10 AM

Tested with v.2.1 of the plugin (mvn.bat org.apache.maven.plugins:maven-eclipse-plugin:2.1:eclipse) - version 2.1 doesn't have this problem.

Show
Jan-Helge Bergesen added a comment - 26/Apr/06 7:10 AM Tested with v.2.1 of the plugin (mvn.bat org.apache.maven.plugins:maven-eclipse-plugin:2.1:eclipse) - version 2.1 doesn't have this problem.
Hide
Permalink
Alexandre Poitras added a comment - 04/Jul/06 1:36 PM

Use ${pom.build.output.directory} instead of ${basedir} and everything works.

Show
Alexandre Poitras added a comment - 04/Jul/06 1:36 PM Use ${pom.build.output.directory} instead of ${basedir} and everything works.
Hide
Permalink
Pablo Francavilla added a comment - 08/Nov/06 2:29 PM

I try with org.apache.maven.plugins:maven-eclipse-plugin:2.1:eclipse and I've the same error.

[INFO] ------------------------------------------------------------------------
[ERROR] BUILD ERROR
[INFO] ------------------------------------------------------------------------
[INFO] Can't canonicalize system path: C:\TGS001\app-web\C:\TGS001\app-web\main\webapp

Embedded error: El nombre de archivo, directorio o etiqueta del volumen no es vßlido
[INFO] ------------------------------------------------------------------------
[INFO] Trace
org.apache.maven.lifecycle.LifecycleExecutionException: Can't canonicalize system path: C:\TGS001\app-web\C:\TGS001\app-
web\main\webapp
at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:559)
at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeStandaloneGoal(DefaultLifecycleExecutor.java:488)
at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:458)
at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.jav
a:306)
at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:273)
at org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:140)
at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:322)
at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:115)
at org.apache.maven.cli.MavenCli.main(MavenCli.java:256)
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:324)
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)
Caused by: org.apache.maven.plugin.MojoExecutionException: Can't canonicalize system path: C:\TGS001\app-web\C:\TGS001\a
pp-web\main\webapp
at org.apache.maven.plugin.eclipse.EclipseUtils.toRelativeAndFixSeparator(EclipseUtils.java:78)
at org.apache.maven.plugin.eclipse.writers.EclipseWtpComponentWriter.writeModuleTypeComponent(EclipseWtpComponen
tWriter.java:130)
at org.apache.maven.plugin.eclipse.writers.EclipseWtpComponentWriter.write(EclipseWtpComponentWriter.java:86)
at org.apache.maven.plugin.eclipse.EclipsePlugin.write(EclipsePlugin.java:397)
at org.apache.maven.plugin.eclipse.EclipsePlugin.execute(EclipsePlugin.java:356)
at org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:412)
at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:534)
... 16 more
Caused by: java.io.IOException: El nombre de archivo, directorio o etiqueta del volumen no es vßlido
at java.io.WinNTFileSystem.canonicalize0(Native Method)
at java.io.Win32FileSystem.canonicalize(Win32FileSystem.java:354)
at java.io.File.getCanonicalPath(File.java:513)
at org.apache.maven.plugin.eclipse.EclipseUtils.toRelativeAndFixSeparator(EclipseUtils.java:74)
... 22 more

Note that the path is wrong formed.

If I use ${pom.build.output.directory} instead of ${basedir} the eclipse:eclipse goal build sucessfully, but when run mvn install, the war building fail.

Show
Pablo Francavilla added a comment - 08/Nov/06 2:29 PM I try with org.apache.maven.plugins:maven-eclipse-plugin:2.1:eclipse and I've the same error. [INFO] ------------------------------------------------------------------------ [ERROR] BUILD ERROR [INFO] ------------------------------------------------------------------------ [INFO] Can't canonicalize system path: C:\TGS001\app-web\C:\TGS001\app-web\main\webapp Embedded error: El nombre de archivo, directorio o etiqueta del volumen no es vßlido [INFO] ------------------------------------------------------------------------ [INFO] Trace org.apache.maven.lifecycle.LifecycleExecutionException: Can't canonicalize system path: C:\TGS001\app-web\C:\TGS001\app- web\main\webapp at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:559) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeStandaloneGoal(DefaultLifecycleExecutor.java:488) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:458) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.jav a:306) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:273) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:140) at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:322) at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:115) at org.apache.maven.cli.MavenCli.main(MavenCli.java:256) 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:324) 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) Caused by: org.apache.maven.plugin.MojoExecutionException: Can't canonicalize system path: C:\TGS001\app-web\C:\TGS001\a pp-web\main\webapp at org.apache.maven.plugin.eclipse.EclipseUtils.toRelativeAndFixSeparator(EclipseUtils.java:78) at org.apache.maven.plugin.eclipse.writers.EclipseWtpComponentWriter.writeModuleTypeComponent(EclipseWtpComponen tWriter.java:130) at org.apache.maven.plugin.eclipse.writers.EclipseWtpComponentWriter.write(EclipseWtpComponentWriter.java:86) at org.apache.maven.plugin.eclipse.EclipsePlugin.write(EclipsePlugin.java:397) at org.apache.maven.plugin.eclipse.EclipsePlugin.execute(EclipsePlugin.java:356) at org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:412) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:534) ... 16 more Caused by: java.io.IOException: El nombre de archivo, directorio o etiqueta del volumen no es vßlido at java.io.WinNTFileSystem.canonicalize0(Native Method) at java.io.Win32FileSystem.canonicalize(Win32FileSystem.java:354) at java.io.File.getCanonicalPath(File.java:513) at org.apache.maven.plugin.eclipse.EclipseUtils.toRelativeAndFixSeparator(EclipseUtils.java:74) ... 22 more Note that the path is wrong formed. If I use ${pom.build.output.directory} instead of ${basedir} the eclipse:eclipse goal build sucessfully, but when run mvn install, the war building fail.
Hide
Permalink
Arnaud Heritier added a comment - 20/Apr/09 5:39 PM

It is a core problem fixed in maven 2.1.0.

Show
Arnaud Heritier added a comment - 20/Apr/09 5:39 PM It is a core problem fixed in maven 2.1.0.
Hide
Permalink
Eduardo Guimarães added a comment - 09/Sep/09 1:22 PM - edited

Using:
Maven 2.2.1
Java 1.6.0_16
Microsoft Windows XP [versão 5.1.2600]
Eclipse Galileo 3.5

For some reason, my installed Maven doesn't parses a directory path anymore. When using ${basedir}/src/main/estatico a FileNotFoundException error occurs. The solution was to avoid the usage of ${basedir} in resouces tags of pom files.

Build errors for perseus-webapp

org.apache.maven.lifecycle.LifecycleExecutionException: Internal error in the plugin manager executing goal 'org.apache.maven.plugins:maven-resources-plugin:2.2:resources': Mojo execution failed.
at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:505)
at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegmentForProject(DefaultLifecycleExecutor.java:265)
at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:191)
at org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:149)
at org.apache.maven.DefaultMaven.execute_aroundBody0(DefaultMaven.java:223)
at org.apache.maven.DefaultMaven.execute_aroundBody1$advice(DefaultMaven.java:304)
at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:1)
at org.apache.maven.embedder.MavenEmbedder.execute_aroundBody2(MavenEmbedder.java:904)
at org.apache.maven.embedder.MavenEmbedder.execute_aroundBody3$advice(MavenEmbedder.java:304)
at org.apache.maven.embedder.MavenEmbedder.execute(MavenEmbedder.java:1)
at org.maven.ide.eclipse.internal.project.DefaultBuildParticipant$1.execute(DefaultBuildParticipant.java:130)
at org.maven.ide.eclipse.internal.project.MavenProjectManagerImpl.execute(MavenProjectManagerImpl.java:986)
at org.maven.ide.eclipse.internal.project.MavenProjectFacade.execute(MavenProjectFacade.java:320)
at org.maven.ide.eclipse.internal.project.DefaultBuildParticipant.executePostBuild(DefaultBuildParticipant.java:116)
at org.maven.ide.eclipse.internal.project.DefaultBuildParticipant.build(DefaultBuildParticipant.java:80)
at org.maven.ide.eclipse.internal.builder.MavenBuilder.build(MavenBuilder.java:84)
at org.eclipse.core.internal.events.BuildManager$2.run(BuildManager.java:627)
at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42)
at org.eclipse.core.internal.events.BuildManager.basicBuild(BuildManager.java:170)
at org.eclipse.core.internal.events.BuildManager.basicBuild(BuildManager.java:201)
at org.eclipse.core.internal.events.BuildManager$1.run(BuildManager.java:253)
at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42)
at org.eclipse.core.internal.events.BuildManager.basicBuild(BuildManager.java:256)
at org.eclipse.core.internal.events.BuildManager.basicBuildLoop(BuildManager.java:309)
at org.eclipse.core.internal.events.BuildManager.build(BuildManager.java:341)
at org.eclipse.core.internal.events.AutoBuildJob.doBuild(AutoBuildJob.java:140)
at org.eclipse.core.internal.events.AutoBuildJob.run(AutoBuildJob.java:238)
at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55)
Caused by: org.apache.maven.plugin.PluginExecutionException: Mojo execution failed.
at org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:601)
at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:498)
... 27 more
Caused by: org.apache.maven.plugin.MojoExecutionException: Error copying resources
at org.apache.maven.plugin.resources.ResourcesMojo.copyResources(ResourcesMojo.java:187)
at org.apache.maven.plugin.resources.ResourcesMojo.execute(ResourcesMojo.java:100)
at org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:579)
... 28 more
Caused by: java.io.FileNotFoundException: D:\Projetos\workspace\Galileo\pegasus\pegasus-webapp\target\classes\D:\Projetos\workspace\Galileo\pegasus\pegasus-webapp\target\pegasus-webapp\css\common.css (A sintaxe do nome do arquivo, pasta ou nome do volume está incorreta)
at java.io.FileOutputStream.open(Native Method)
at java.io.FileOutputStream.<init>(FileOutputStream.java:179)
at java.io.FileOutputStream.<init>(FileOutputStream.java:131)
at org.codehaus.plexus.util.FileUtils.copyFile(FileUtils.java:797)
at org.apache.maven.plugin.resources.ResourcesMojo.copyFile(ResourcesMojo.java:228)
at org.apache.maven.plugin.resources.ResourcesMojo.copyResources(ResourcesMojo.java:183)
... 30 more

Show
Eduardo Guimarães added a comment - 09/Sep/09 1:22 PM - edited Using: Maven 2.2.1 Java 1.6.0_16 Microsoft Windows XP [versão 5.1.2600] Eclipse Galileo 3.5 For some reason, my installed Maven doesn't parses a directory path anymore. When using ${basedir}/src/main/estatico a FileNotFoundException error occurs. The solution was to avoid the usage of ${basedir} in resouces tags of pom files. Build errors for perseus-webapp org.apache.maven.lifecycle.LifecycleExecutionException: Internal error in the plugin manager executing goal 'org.apache.maven.plugins:maven-resources-plugin:2.2:resources': Mojo execution failed. at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:505) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegmentForProject(DefaultLifecycleExecutor.java:265) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:191) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:149) at org.apache.maven.DefaultMaven.execute_aroundBody0(DefaultMaven.java:223) at org.apache.maven.DefaultMaven.execute_aroundBody1$advice(DefaultMaven.java:304) at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:1) at org.apache.maven.embedder.MavenEmbedder.execute_aroundBody2(MavenEmbedder.java:904) at org.apache.maven.embedder.MavenEmbedder.execute_aroundBody3$advice(MavenEmbedder.java:304) at org.apache.maven.embedder.MavenEmbedder.execute(MavenEmbedder.java:1) at org.maven.ide.eclipse.internal.project.DefaultBuildParticipant$1.execute(DefaultBuildParticipant.java:130) at org.maven.ide.eclipse.internal.project.MavenProjectManagerImpl.execute(MavenProjectManagerImpl.java:986) at org.maven.ide.eclipse.internal.project.MavenProjectFacade.execute(MavenProjectFacade.java:320) at org.maven.ide.eclipse.internal.project.DefaultBuildParticipant.executePostBuild(DefaultBuildParticipant.java:116) at org.maven.ide.eclipse.internal.project.DefaultBuildParticipant.build(DefaultBuildParticipant.java:80) at org.maven.ide.eclipse.internal.builder.MavenBuilder.build(MavenBuilder.java:84) at org.eclipse.core.internal.events.BuildManager$2.run(BuildManager.java:627) at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42) at org.eclipse.core.internal.events.BuildManager.basicBuild(BuildManager.java:170) at org.eclipse.core.internal.events.BuildManager.basicBuild(BuildManager.java:201) at org.eclipse.core.internal.events.BuildManager$1.run(BuildManager.java:253) at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42) at org.eclipse.core.internal.events.BuildManager.basicBuild(BuildManager.java:256) at org.eclipse.core.internal.events.BuildManager.basicBuildLoop(BuildManager.java:309) at org.eclipse.core.internal.events.BuildManager.build(BuildManager.java:341) at org.eclipse.core.internal.events.AutoBuildJob.doBuild(AutoBuildJob.java:140) at org.eclipse.core.internal.events.AutoBuildJob.run(AutoBuildJob.java:238) at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55) Caused by: org.apache.maven.plugin.PluginExecutionException: Mojo execution failed. at org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:601) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:498) ... 27 more Caused by: org.apache.maven.plugin.MojoExecutionException: Error copying resources at org.apache.maven.plugin.resources.ResourcesMojo.copyResources(ResourcesMojo.java:187) at org.apache.maven.plugin.resources.ResourcesMojo.execute(ResourcesMojo.java:100) at org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:579) ... 28 more Caused by: java.io.FileNotFoundException: D:\Projetos\workspace\Galileo\pegasus\pegasus-webapp\target\classes\D:\Projetos\workspace\Galileo\pegasus\pegasus-webapp\target\pegasus-webapp\css\common.css (A sintaxe do nome do arquivo, pasta ou nome do volume está incorreta) at java.io.FileOutputStream.open(Native Method) at java.io.FileOutputStream.<init>(FileOutputStream.java:179) at java.io.FileOutputStream.<init>(FileOutputStream.java:131) at org.codehaus.plexus.util.FileUtils.copyFile(FileUtils.java:797) at org.apache.maven.plugin.resources.ResourcesMojo.copyFile(ResourcesMojo.java:228) at org.apache.maven.plugin.resources.ResourcesMojo.copyResources(ResourcesMojo.java:183) ... 30 more

People

  • Assignee:
    Unassigned
    Reporter:
    Jan-Helge Bergesen
Vote (2)
Watch (2)

Dates

  • Created:
    26/Apr/06 6:47 AM
    Updated:
    11/Sep/09 1:29 PM
    Resolved:
    20/Apr/09 5:39 PM
  • Atlassian JIRA (v5.0.4#731-sha1:3aa7374)
  • Report a problem
  • Powered by a free Atlassian JIRA open source license for Codehaus. Try JIRA - bug tracking software for your team.