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

Jörg Schaible commented on MNG-5207:
------------------------------------

Hi Stephen,

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

Unfortunately it is no option to sort the modules if you deal with about Maven 
400 projects nested multiple levels deep. We have some components there which 
provides services as EJB and their implementation will use other component's 
EJB clients. Maintaining the build order manually would be a nightmare.

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

This is even wrong, because your app should *not* contain the ejb nor their 
dependencies (those are implementation details), if those dependencies are not 
exposed through the EJB's API. Typically we declare the ejb-client dependency 
with a lot of exclusions.

BTW: Thanks for investigation. M221 must have taken the transitive deps into 
account. IMHO this will also solve MNG-5472

> [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