maven-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Stephen Evanchik (JIRA)" <j...@codehaus.org>
Subject [jira] Created: (MNG-3751) Multi-module project is non-deterministic in evaluating reactor artifacts defined as dependencies unless they are installed in the local repository
Date Thu, 11 Sep 2008 16:43:49 GMT
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
          Issue Type: Bug
          Components: Artifacts and Repositories, Dependencies, Reactor and workspace
    Affects Versions: 2.0.9, 2.0.8
         Environment: Mac OS X 10.5.4, Windows XP SPx, CentOS 5.2
            Reporter: Stephen Evanchik
         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

        

Mime
View raw message