[jbosstools-issues] [JBoss JIRA] (JBIDE-14589) Incorrect "Build path contains duplicate entry" report
Rastislav Wagner (JIRA)
jira-events at lists.jboss.org
Mon May 27 08:56:06 EDT 2013
[ https://issues.jboss.org/browse/JBIDE-14589?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Rastislav Wagner closed JBIDE-14589.
------------------------------------
verified in JBDS 7.0.0 Beta1-v20130526-0839-B241
> Incorrect "Build path contains duplicate entry" report
> ------------------------------------------------------
>
> Key: JBIDE-14589
> URL: https://issues.jboss.org/browse/JBIDE-14589
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: maven
> Affects Versions: 4.1.0.Alpha2
> Environment: Windows 7 64-bit, Kepler M7 Java EE package, m2e 1.4, m2e-wtp 1.0.0
> Reporter: Stanimir Stamenkov
> Assignee: Fred Bricon
> Labels: respin-a
> Fix For: 4.1.0.Beta1
>
> Attachments: sample-project.zip
>
>
> Sample project:
> {noformat}
> pom.xml
> resources/
> foo
> bar
> child-module/
> pom.xml
> other-module/
> pom.xml
> {noformat}
> {code:xml|title=child-module/pom.xml}
> <project>
> ...
> <build>
> <resources>
> <resource>
> <directory>${basedir}/../resources</directory>
> <includes>
> <include>foo</include>
> </includes>
> </resource>
> </resources>
> ...
> {code}
> {code:xml|title=other-module/pom.xml}
> <project>
> ...
> <build>
> <resources>
> <resource>
> <directory>${basedir}/../resources</directory>
> <includes>
> <include>foo</include>
> <include>bar</include>
> </includes>
> </resource>
> </resources>
> ...
> {code}
> Importing it into Eclipse with current JBoss Tools 4.1 (Abridged Tools):
> {noformat:title=Error Updating Maven Configuration}
> Unable to update maven configuration for the following projects:
> child-module | Build path contains duplicate entry: '/.../resources' for project 'child-module'
> other-module | Build path contains duplicate entry: '/.../resources' for project 'other-module'
> {noformat}
> Uninstalling the "JBoss Maven Seam configurator" (disabling it wasn't sufficient) made the problem disappear.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
More information about the jbosstools-issues
mailing list