[ 
https://issues.apache.org/jira/browse/MNG-8191?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17872403#comment-17872403
 ] 

Reto Hoehener commented on MNG-8191:
------------------------------------

We generate a reactor pom that contains every project in our flat SCM 
structure. This reactor pom is very convenient for CI builds, or 
license/coverage/codestyle analysis. But it means there is no straightforward 
inheritance relationship (or any relationship at all) between some of these 
modules.

So yes, our BOMs are inter-project, but our reactor as well...

> [reactor build order] modules used in dependencyManagement-section with scope 
> import should be ordered first
> ------------------------------------------------------------------------------------------------------------
>
>                 Key: MNG-8191
>                 URL: https://issues.apache.org/jira/browse/MNG-8191
>             Project: Maven
>          Issue Type: Bug
>          Components: Reactor and Workspace
>    Affects Versions: 3.0
>            Reporter: Reto Hoehener
>            Priority: Major
>
> I asked about this on Stack Overflow: 
> [https://stackoverflow.com/questions/77060268/why-is-an-imported-pom-module-not-ordered-at-the-beginning-of-the-maven-multi-mo]
> I value the responses by Karl Heinz Marbaise but would kindly ask the Maven 
> community to consider this again.
> I understand that the management sections do not actually declare 
> dependencies (or plugins). But - same as a parent pom - they do manage 
> versions, which can affect the actual versions used for real dependencies and 
> plugins.
> I will of course provide more examples or details if necessary.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

Reply via email to