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

**[Robert Scholte](https://issues.apache.org/jira/secure/ViewProfile.jspa?name=rfscholte)** opened **[MPH-183](https://issues.apache.org/jira/browse/MPH-183?redirect=false)** and commented

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.

---

**Affects:** 3.2.0

**Attachments:**
- [mph-183-it.zip](https://issues.apache.org/jira/secure/attachment/13034986/mph-183-it.zip) (_5.96 kB_)

**Issue Links:**
- [MNG-3220](https://issues.apache.org/jira/browse/MNG-3220) Allow managed dependencies to be imported into other projects
(_**"is caused by"**_)
- [MNG-7906](https://issues.apache.org/jira/browse/MNG-7906) Dependency Management import (BOM) does not work the "maven way"

- [MNG-7344](https://issues.apache.org/jira/browse/MNG-7344) Effective pom should contain more finegrained details regarding its content origin: track dependencyManagement import
(_**"requires"**_)
- [MPH-160](https://issues.apache.org/jira/browse/MPH-160) help:effective-pom -Dverbose: add source location as comments in effective pom.xml
(_**"supercedes"**_)

**Remote Links:**
- [GitHub Pull Request #37
](https://github.com/apache/maven-help-plugin/pull/37)
- [GitHub Pull Request #603
](https://github.com/apache/maven/pull/603)

2 votes, 5 watchers