[
https://issues.apache.org/jira/browse/MNG-8191?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17872378#comment-17872378
]
Tamas Cservenak commented on MNG-8191:
--------------------------------------
BOMs are meant for "inter project" version management mainly. In reactor (so
within one multi module build) use rather plain inheritance. So, one is for
"export/import" (across project borders) while the other is meant for "domestic
use".
> [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)
