[
http://jira.codehaus.org/browse/MECLIPSE-608?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=205307#action_205307
]
Matthew McCullough commented on MECLIPSE-608:
---------------------------------------------
Typically, the cause of this is because a POM author put a replaceable like
${basedir} in the target or directory tags. This is not allowed. Target and
Directory tags are relative to the POM, and are not supposed to have drive
letters and paths to roots of the filesystem.
http://maven.apache.org/ref/2.2.1/maven-model/maven.html#class_resource
If you remove the ${basedir} type references from the paths, the plugin works
just fine.
Similar to:
http://jira.codehaus.org/browse/MECLIPSE-269
> "Can't canonicalize system path" error using the goal eclispse:eclipse
> ----------------------------------------------------------------------
>
> Key: MECLIPSE-608
> URL: http://jira.codehaus.org/browse/MECLIPSE-608
> Project: Maven 2.x Eclipse Plugin
> Issue Type: Bug
> Affects Versions: 2.7
> Environment: Maven 2.2.1
> JDK 1.6.0_14
> Windows XP
> Reporter: Cyril Delmas
> Attachments: cgin-apps-archetype.zip, maven.log
>
>
> I've created an archetype (see attached archive). I generate a project using
> this archetype, then I try to generate the eclipse files with eclipse:eclipse
> (eclipse:m2eclipse gives the same), then I get the following error :
> "Cant canonicalize system path: {0}".
> As an attachment, I give the archetype and the complete stack trace.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
