You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Tamas Cservenak (Jira)" <ji...@apache.org> on 2023/10/13 20:03:00 UTC
[jira] [Created] (MNG-7906) Dependency Management import does not work the "maven way"
Tamas Cservenak created MNG-7906:
------------------------------------
Summary: Dependency Management import does not work the "maven way"
Key: MNG-7906
URL: https://issues.apache.org/jira/browse/MNG-7906
Project: Maven
Issue Type: Bug
Components: Dependencies
Reporter: Tamas Cservenak
This affects all released Maven versions so far.
Problem reproducer: https://github.com/cstamas/MNG-7852 (repo name is wrong, obviously).
In short: unlike with dependencies, where you CAN override some "deep transitive" dependency by re-declaring it directly as 1st level dependency in POM, for depMgt import this does not work, actually, it works quite the opposite ("first comes, wins"). Moreover, Maven remains silent about this, as reproducer shows, and all of this goes unnoticed.
Solution: at least depMgt import should make "the maven way", maybe not by default (to not break existing builds) but configurable. Problem is solved if in reproducer:
- with fix enabled, junit 5.9.3 is used, AND
- with fix disabled, Maven yells about ignored depMgt
--
This message was sent by Atlassian Jira
(v8.20.10#820010)