[ https://issues.apache.org/jira/browse/MNG-7344?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17832592#comment-17832592 ]
Maarten Mulders commented on MNG-7344: -------------------------------------- [~gnodet] agreed. I don't think backporting to Maven 3.x is worth the effort, seeing how much work has been necessary to get this to a working point. > Effective pom should contain more finegrained details regarding its content > origin: track dependencyManagement import > --------------------------------------------------------------------------------------------------------------------- > > Key: MNG-7344 > URL: https://issues.apache.org/jira/browse/MNG-7344 > Project: Maven > Issue Type: Improvement > Components: Inheritance and Interpolation, POM > Reporter: Robert Scholte > Priority: Major > Fix For: 3.9.x-candidate, 4.0.x-candidate > > Attachments: MicrosoftTeams-image.png > > > To support MPH-183 some changes needs to be done in Maven Core. > For every element that is not part of the raw model, it must be possible to > get the "resolution path" to that element. > Until now, only the usual pure inheritance is tracked though InputLocation, > as done in MNG-1803, later displayed by verbose help effective-pom with > MPH-160 > The following are known to add elements to the effective pom: > - BOMs dependencyManagement import > - [Tiles Maven Plugin|https://github.com/repaint-io/maven-tiles] by [~talios] > Without this feature, it is very hard to detect where these extra elements > are coming from. -- This message was sent by Atlassian Jira (v8.20.10#820010)