[
https://issues.apache.org/jira/browse/MNG-7344?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17863837#comment-17863837
]
ASF GitHub Bot commented on MNG-7344:
-------------------------------------
gnodet commented on PR #603:
URL: https://github.com/apache/maven/pull/603#issuecomment-2214474841
The changes to `DefaultModelBuilder` and
`DefaultDependencyManagementImporter` need to be moved from
`maven-model-builder` to the implementations in `maven-api-impl`, as the ones
from `maven-model-builder` are kept for compatibility but are not used anymore.
> 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)
