[MNG-7854] Non directly managed imported and conflicting depMgt entries should warn

• Type: Improvement
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Fix Version/s: 4.0.0-alpha-13, 4.0.0
• Component/s: POM
• Assignee: Tamas Cservenak
• Reporter: Tamas Cservenak
• Created: 27/Jul/23 11:39
• Updated: 13/May/24 15:23
• Resolved: 01/Feb/24 16:25

Description

The artificial (or "bolted on") scope "import" behaves wildly differently that rest of Maven, causes surprise to our users. For start, we should emit "actionable" warnings about these, ultimate goal is to align this behaviour with "maven way" of working ("closest occurence wins" vs current weird "direct occurrence then first occurence wins" strategy)

See https://github.com/cstamas/MNG-7852 for reproducer.

Issue Links

• causes: MNG-8078 BOM POM import warnings are emitted on scopes and exclusions
• relates to: MNG-7906 Dependency Management import (BOM) does not work the "maven way"
• links to: GitHub Pull Request #1211
• links to: GitHub Pull Request #1370