Details
-
Type:
Improvement
-
Status:
Open
-
Priority:
Major
-
Resolution: Unresolved
-
Affects Version/s: 2.5
-
Fix Version/s: None
-
Labels:None
-
Environment:Maven version: 2.0.8
Java version: 1.6.0_05
OS name: "windows xp" version: "5.1" arch: "x86" Family: "windows"
-
Testcase included:yes
-
Number of attachments :
Description
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:
<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>
When executing
mvn eclipse:eclipse
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.