[
http://jira.codehaus.org/browse/MECLIPSE-676?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=251923#action_251923
]
Ulf B. commented on MECLIPSE-676:
---------------------------------
I got exactly the same problem always appearing when eclipse 3.6 is replacing
the location-tag with the locationURI-tag. The eclipse-plugin is noticing, that
there's already a linkedResource and is not replacing it but reminds you with
the error shown in the question above.
A eclipse:clean is solving my problem temporarily but i can't and i won't
always eclipse:clean before, because it's additional time running each
eclipse:eclipse and its deleting the projects module dependencies i have to
append manually afterwards. The plugin itself creates <location>-Tags if theres
no entry already existing.
> linkedResources: <location> vs <locationURI>
> --------------------------------------------
>
> Key: MECLIPSE-676
> URL: http://jira.codehaus.org/browse/MECLIPSE-676
> Project: Maven 2.x Eclipse Plugin
> Issue Type: Bug
> Components: Core : .project
> Affects Versions: 2.8
> Environment: Elipse 3.6, mvn 2.2.1, Mac OS X 10.6.5
> Reporter: Lutz Huehnken
>
> When creating a link to another folder in Eclipse 3.6, it will generate a
> snippet like this in the .project:
> <linkedResources>
> <link>
> <name>src/main/webapp/docroot/myfolder</name>
> <type>2</type>
>
> <locationURI>FOLDER_VAR/otherfolder/myfolder</locationURI>
> </link>
> </linkedResources>
> When running eclipse:eclipse, the parsing / update of .project will fail with:
> java.lang.IllegalArgumentException: No location node.
> at
> org.apache.maven.plugin.eclipse.LinkedResource.<init>(LinkedResource.java:110)
> at
> org.apache.maven.plugin.eclipse.writers.EclipseProjectWriter.write(EclipseProjectWriter.java:155)
> at
> org.apache.maven.plugin.eclipse.EclipsePlugin.writeConfiguration(EclipsePlugin.java:1139)
> Apparently, the plugin expects the element <location> rather than
> <locationURI>, which seems to be a bug.
--
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
