[ 
https://jira.codehaus.org/browse/MNG-5207?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=341803#comment-341803
 ] 

Stephen Connolly commented on MNG-5207:
---------------------------------------

FYI the workaround is to change

{code}
  <modules>
    <module>app</module>
    <module>delegate</module>
    <module>ejb</module>
  </modules>
{code}

to 

{code}
  <modules>
    <module>delegate</module>
    <module>ejb</module>
    <module>app</module>
  </modules>
{code}  

The project sorter will correctly pull ejb ahead of delegate and respects the 
order in the modules unless direct dependencies indicate otherwise.

A rule of thumb to avoid this issue is that you should list leaf modules first 
and put modules with transitive dependencies last... 

Another solution is just to add the dependency of ejb to app and again the 
project sorter will sort correctly.

I am currently investigating whether the project sorter is running prior to 
dependency resolution. It may be acceptable to resolve ex-reactor dependencies 
as early as the project sorter as if they are unavailable we will fail 
anyway... though plugins such as shade could make them available later in the 
reactor build... perhaps it is acceptable to just produce a best effort sorting 
if ex-reactor dependencies are not available when sorting the projects

> [Regression] Maven 3 fails to calculate proper build order with dependencies 
> with classifiers
> ---------------------------------------------------------------------------------------------
>
>                 Key: MNG-5207
>                 URL: https://jira.codehaus.org/browse/MNG-5207
>             Project: Maven 2 & 3
>          Issue Type: Bug
>          Components: Reactor and workspace
>    Affects Versions: 3.0.3
>            Reporter: Jörg Schaible
>            Assignee: Jason van Zyl
>            Priority: Critical
>             Fix For: Issues to be reviewed for 4.x
>
>         Attachments: mng5207-it.tgz, mng-5207-minimal.tar.gz, MNG-5207.tgz
>
>
> Maven 3.0.3 and 3.0.4 RC1 fails to build the projects of the reactor in 
> proper order, if a transitive dependency (that is part of the reactor build) 
> is overruled in the dependencyManagement section with the current SNAPSHOT 
> version. Build order is perfectly calculated with Maven 2.2.1.



--
This message was sent by Atlassian JIRA
(v6.1.6#6162)

Reply via email to