You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Jason van Zyl (JIRA)" <ji...@codehaus.org> on 2009/12/30 21:21:55 UTC
[jira] Updated: (MNG-3751) Multi-module project is
non-deterministic in evaluating reactor artifacts defined as dependencies
unless they are installed in the local repository
[ http://jira.codehaus.org/browse/MNG-3751?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jason van Zyl updated MNG-3751:
-------------------------------
Fix Version/s: (was: 2.x)
3.0-alpha-7
> Multi-module project is non-deterministic in evaluating reactor artifacts defined as dependencies unless they are installed in the local repository
> ---------------------------------------------------------------------------------------------------------------------------------------------------
>
> Key: MNG-3751
> URL: http://jira.codehaus.org/browse/MNG-3751
> Project: Maven 2 & 3
> Issue Type: Bug
> Components: Artifacts and Repositories, Dependencies, Reactor and workspace
> Affects Versions: 2.0.8, 2.0.9
> Environment: Mac OS X 10.5.4, Windows XP SPx, CentOS 5.2
> Reporter: Stephen Evanchik
> Fix For: 3.0-alpha-7
>
> Attachments: full-dependency-tree.txt, master-compile-run.txt, maven-test.tar.gz
>
>
> Summary: Multi-module project is non-deterministic in evaluating reactor artifacts defined as dependencies unless they are installed in the local repository
> I cannot build either a leaf project (sub1-module1) or the master project (master) until I 'mvn install' the sub-modules (sub<N>-module<M>).
> I believe that dependency modules found only in the reactor should be added to:
> [DEBUG] (f) classpathElements = [/Users/evanchsa/src/maven-test/subproject1/sub1-module1/target/classes]
> Detailed setup:
> I have a multi-module project that is laid out in the following POM inheritance (this is not the filesystem layout):
> master
> + sub1-master
> - sub1-module1
> - sub1-module2
> + sub2-master
> - sub2-module1
> - sub2-module2
> Sub-modules are type "jar" and 1 "war" and there are dependencies within the sub-modules as follows (using mvn dependency:tree):
> 1. sub1-module1
> - Depends on no other modules
> 2. sub1-module2
> - test-group:sub1-module2:jar:0.0.1
> \- test-group:sub1-module1:jar:0.0.1:compile
> 3. sub2-module1
> - test-group:sub2-module1:jar:0.0.1
> \- test-group:sub1-module2:jar:0.0.1:compile
> \- test-group:sub1-module1:jar:0.0.1:compile
> 4. sub2-module2 (this is the WAR)
> - test-group:sub2-module2:jar:0.0.1
> \- test-group:sub2-module1:jar:0.0.1:compile
> \- test-group:sub1-module2:jar:0.0.1:compile
> \- test-group:sub1-module1:jar:0.0.1:compile
> Project filesystem layout:
> build/master/pom.xml
> subproject1/sub1-master/pom.xml
> subproject1/sub1-module1/pom.xml
> subproject1/sub1-module2/pom.xml
> subproject2/sub2-master/pom.xml
> subproject2/sub2-module1/pom.xml
> subproject2/sub2-module2/pom.xml
--
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