[MPH-183] Effective-pom + verbose should show import path to BOM dependencyManagement

• Type: Improvement
• Status: Open
• Priority: Major
• Resolution: Unresolved
• Affects Version/s: 3.2.0
• Assignee: Maarten Mulders
• Reporter: Robert Scholte
• Created: 15/Oct/21 12:16
• Updated: 07/Jun/24 11:55

Description

The popular spring-boot makes a lot of use of BOMs. Using BOMs is a good practice, but right now it is very hard to determine where dependencyManagement dependencies and especially their versions are coming from.

Instead of only showing only the final location (from the BOM POM), it should also show the import path from the current project to that specific pom (where is the BOM POM imported?).

This way it will be easier to figure out which dependency in which POM needs to be upgraded: it's the version in the POM declaring the import of the BOM POM, not the version in the imported BOM POM.

Issue Links

• is related to: MNG-7906 Dependency Management import (BOM) does not work the "maven way"
• requires: MNG-7344 Effective pom should contain more finegrained details regarding its content origin: track dependencyManagement import
• supercedes: MPH-160 help:effective-pom -Dverbose: add source location as comments in effective pom.xml
• links to: GitHub Pull Request #37
• links to: GitHub Pull Request #603