eclipse:eclipse on pom with modules: order of entries in .classpath
-------------------------------------------------------------------
Key: MECLIPSE-420
URL: http://jira.codehaus.org/browse/MECLIPSE-420
Project: Maven 2.x Eclipse Plugin
Issue Type: Improvement
Components: Core : Dependencies resolution and build path, 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 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
