[
https://issues.apache.org/jira/browse/MECLIPSE-420?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Osipov closed MECLIPSE-420.
-----------------------------------
Resolution: Auto Closed
This issue has been auto closed because it has been inactive for a long period
of time. If you think this issue still applies, retest your problem with the
most recent version of Maven and the affected component, reopen and post your
results.
> eclipse:eclipse on pom with modules: order of entries in .classpath
> -------------------------------------------------------------------
>
> Key: MECLIPSE-420
> URL: https://issues.apache.org/jira/browse/MECLIPSE-420
> Project: Maven Eclipse Plugin
> Issue Type: Improvement
> Components: Core : Dependencies resolution and build path
> (.classpath), Core : Multi-projects
> Affects Versions: 2.5
> Environment: Maven version: 2.0.8
> Java version: 1.6.0_05
> OS name: "windows xp" version: "5.1" arch: "x86" Family: "windows"
> Reporter: Sebastian Jacobi
> Attachments: test.zip
>
>
> I have three modules: module1, module2 and module3.
> Module2 depends on module1 (with some dependency inclusions) and module3
> depends on module2 (and indirectly on module1).
> Now I created a "super pom" as follows:
> {code:xml}
> <project xmlns="http://maven.apache.org/POM/4.0.0";
> xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";
> xsi:schemaLocation="http://maven.apache.org/POM/4.0.0
> http://maven.apache.org/xsd/maven-4.0.0.xsd";>
> <modelVersion>4.0.0</modelVersion>
> <groupId>com.mycompany.app</groupId>
> <version>1.0-SNAPSHOT</version>
> <artifactId>app</artifactId>
> <packaging>pom</packaging>
> <modules>
> <module>module1</module>
> <module>module2</module>
> <module>module3</module>
> </modules>
> </project>
> {code}
> When executing {noformat}mvn eclipse:eclipse{noformat} on this pom will
> beautifully generate all project and classpath files with the dependencies
> set correctly between the projects (rather than the jars from the maven repo).
> BUT:
> the ordering in the .classpath IMHO should have the referenced projects last
> - as otherwise the excluded dependencies can accidentally take precedence to
> the actually referenced version.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
