[
https://jira.codehaus.org/browse/MNG-5207?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Joerg Schaible updated MNG-5207:
--------------------------------
Attachment: MNG-5207.tgz
Attachment contains demo project. First run script _prepare.sh_ in directory
_prepare_ to populate local repo with necessary stuff (anything uses groupId
_bugs.maven.issue_).
_application_ artifact uses released version of _delegate_ artifact that
depends on a ejb-client dependency which is overruled in the depMgmt section as
snapshot (EJB uses updated runtime dependency to be added in the manifest's
classpath).
Build from root with M303 (or M304rc1) ==> build fails with missing dependency
in _application_.
Build from root with M221 ==> build starts with building _ejb_ component first
and succeeds.
> [Regression] Maven 3 fails to calculate proper build order
> ----------------------------------------------------------
>
> 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: Joerg Schaible
> Priority: Critical
> Attachments: 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 is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
