If you are reasonably convinced its a bug, please go file a bug in
JIRA against the proper component (in this case, the eclipse plugin).
And if you want it fixed (quickly), I'd suggest you pull the plugin
code down, adjust as needed, and contribute it back to be included in
a future release of this plugin.
Wayne
On 5/21/07, Paul Spencer <[EMAIL PROTECTED]> wrote:
Wayne,
So far removing ${basedir} works with the following goals
clean, eclipse:eclipse, package, and war:inplace.
As to "Why do you need it?". Consistency with other path references in
the pom.
If, as it appears, the war plugin uses different rules related to the
prefixing a path with ${basedir}, then I consider it a bug. (just my $0.02)
Paul Spencer
Wayne Fay wrote:
> Remove the ${basedir} from the <warSourceDirectory>?
>
> Why do you need it?
>
> Wayne
>
> On 5/21/07, Paul Spencer <[EMAIL PROTECTED]> wrote:
>> I get a "Can't canonicalize system path" error using the goal
>> eclispse:eclipse when
>> the <warSourceDirectory> of the maven-war-plugin starts with ${basedir}.
>> If I remove the
>> ${basedir}, the build is successful.
>>
>>
>> maven-eclipse-plugin verion 2.3
>> maven-war-plugin verion 2.0.2
>>
>>
>> [INFO]
>> ------------------------------------------------------------------------
>> [ERROR] BUILD ERROR
>> [INFO]
>> ------------------------------------------------------------------------
>> [INFO] Can't canonicalize system path:
>> C:\cvs_apms\ipim-webapp\C:\cvs_apms\ipim-webapp\src\webapp
>>
>> 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:
>> C:\cvs_apms\ipim-webapp\C:\cvs_apms\ipim-webapp\src\webapp
>> at
>>
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:564)
>>
>> at
>>
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeStandaloneGoal(DefaultLifecycleExecutor.java:493)
>>
>> at
>>
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:463)
>>
>> at
>>
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:311)
>>
>> at
>>
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:278)
>>
>> at
>>
org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:143)
>>
>> at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:334)
>> at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:125)
>> at org.apache.maven.cli.MavenCli.main(MavenCli.java:272)
>> 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:\cvs_apms\ipim-webapp\C:\cvs_apms\ipim-webapp\src\webapp
>> at
>> org.apache.maven.plugin.ide.IdeUtils.getCanonicalPath(IdeUtils.java:77)
>> at
>>
org.apache.maven.plugin.ide.IdeUtils.toRelativeAndFixSeparator(IdeUtils.java:89)
>>
>> at
>>
org.apache.maven.plugin.eclipse.writers.EclipseWtpComponentWriter.writeModuleTypeComponent(EclipseWtpComponentWriter.java:142)
>>
>> at
>>
org.apache.maven.plugin.eclipse.writers.EclipseWtpComponentWriter.write(EclipseWtpComponentWriter.java:97)
>>
>> at
>>
org.apache.maven.plugin.eclipse.EclipsePlugin.writeConfiguration(EclipsePlugin.java:671)
>>
>> at
>>
org.apache.maven.plugin.ide.AbstractIdeSupportMojo.execute(AbstractIdeSupportMojo.java:402)
>>
>> at
>>
org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:443)
>>
>> at
>>
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:539)
>>
>> ... 16 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:354)
>> at java.io.File.getCanonicalPath(File.java:513)
>> at
>> org.apache.maven.plugin.ide.IdeUtils.getCanonicalPath(IdeUtils.java:73)
>> ... 23 more
>> [INFO]
>> ------------------------------------------------------------------------
>>
>> Paul Spencer
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: [EMAIL PROTECTED]
>> For additional commands, e-mail: [EMAIL PROTECTED]
>>
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: [EMAIL PROTECTED]
>> For additional commands, e-mail: [EMAIL PROTECTED]
>>
>>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
