[
https://issues.apache.org/jira/browse/MNG-5309?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Osipov updated MNG-5309:
--------------------------------
Fix Version/s: waiting-for-feedback
> InputLocation missing for Xpp3Dom configuration elements
> --------------------------------------------------------
>
> Key: MNG-5309
> URL: https://issues.apache.org/jira/browse/MNG-5309
> Project: Maven
> Issue Type: Bug
> Components: Embedding, IDEs, Inheritance and Interpolation, POM
> Affects Versions: 3.0.4
> Reporter: Milos Kleint
> Assignee: Milos Kleint
> Priority: Major
> Fix For: waiting-for-feedback, Issues to be reviewed for 4.x
>
> Attachments: 2012-07-06_1548.png, mng_configuration.patch
>
>
> I'm trying to create a view over a pom.xml file that displays current
> effective pom, along with showing which line came from which pom. Works more
> or less ok, with the provided InputLocations with one significant exception.
> <configuration> element in <plugin>. See screenshot.
> The idea in the patch is to have the InputLocation tree mimic the tree of
> Xpp3Dom objects. All the merges of Xpp3Dom then manipulate the tree of
> InputLocations as well.
> The patch included is not complete, just proof of concept, needs to have
> proper InputLocation creating in Xpp3DomMavenReaderExt file (I've replaced
> that by some quick post processing, changing modello plugins to generate
> something else is error prone slow to to start with). Additionally the
> default Xpp3Dom merging from plexus-utils is replaced by maven's own version
> of merge code. Not sure there if it's possible/practical to move that code
> down to the dependency.
> also some additional tests are required to be written
--
This message was sent by Atlassian JIRA
(v7.6.14#76016)
