[
https://issues.apache.org/jira/browse/MNG-8191?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17872363#comment-17872363
]
Reto Hoehener edited comment on MNG-8191 at 8/9/24 1:29 PM:
------------------------------------------------------------
[~cstamas] Interesting, thanks for the links. At least I'm not imagining things.
Why are you opting to forbid imported poms in reactor builds?
As long as the dependency tree is an acyclic directed tree, I don't immediately
see why you can't order them first in the reactor and allow it.
I am actually working on removing "BOM POMs" so hopefully this won't affect me
when Maven 4 becomes mainstream, but just for context: currently we have a flat
module structure and some projects import some BOM poms in their dependency
management sections.
was (Author: rho4):
[~cstamas] Interesting, thanks for the links. At least I'm not imagining things.
Why are you opting to forbid imported poms in reactor builds?
As long as the dependency tree is an acyclic directed tree, I don't immediately
see why you can't order it first in the reactor and allow it.
I am actually working on removing "BOM POMs" so hopefully this won't affect me
when Maven 4 becomes mainstream, but just for context: currently we have a flat
module structure and some projects import some BOM poms in their dependency
management sections.
> [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)
