You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Reto Hoehener (Jira)" <ji...@apache.org> on 2024/08/07 13:49:00 UTC
[jira] [Created] (MNG-8191) [reactor build order] modules used in dependencyManagement-section with scope import should be ordered first
Reto Hoehener created MNG-8191:
----------------------------------
Summary: [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
Reporter: Reto Hoehener
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 dependencues (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 example or details if necessary.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)