[MNG-8191] [reactor build order] modules used in dependencyManagement-section with scope import should be ordered first
- Dominant language
- Java
- Stars
- 5.3k
- Forks
- 3.1k
- Avg merge
- 20h 42m
- Merged PRs (30d)
- 297
Description
**[Reto Hoehener](https://issues.apache.org/jira/secure/ViewProfile.jspa?name=rho4)** opened **[MNG-8191](https://issues.apache.org/jira/browse/MNG-8191?redirect=false)** and commented
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.
---
**Affects:** 3.0
**Issue Links:**
- [MNG-8009](https://issues.apache.org/jira/browse/MNG-8009) BOM peculiarities with build ordering
Contributor guide
Assessment
This issue has not been assessed yet.