[
https://issues.apache.org/jira/browse/MPH-160?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Hervé Boutemy updated MPH-160:
------------------------------
Description:
during in-memory effective pom building (by maven-model-builder), the source
location of content is kept in memory: see [Modello documentation on location
tracking|https://codehaus-plexus.github.io/modello/location-tracking.html]
adding this information as comment on every line of generated XML would ease
tracking for end users
This will probably require a Modello enhancement then integration
(idea found during Devoxx 2018 Maven BoF, since users were missing ways to
diagnose unexpected result in effective pom)
was:
during in-memory effective pom building (by maven-model-builder), the source
location of content is kept in memory
adding this information as comment on every line of generated XML would ease
tracking for end users
(idea found during Devoxx 2018 Maven BoF, since users were missing ways to
diagnose unexpected result in effective pom)
> add source location in comments to effective pom.xml
> ----------------------------------------------------
>
> Key: MPH-160
> URL: https://issues.apache.org/jira/browse/MPH-160
> Project: Maven Help Plugin
> Issue Type: New Feature
> Components: effective-pom
> Affects Versions: 3.1.0
> Reporter: Hervé Boutemy
> Priority: Major
>
> during in-memory effective pom building (by maven-model-builder), the source
> location of content is kept in memory: see [Modello documentation on location
> tracking|https://codehaus-plexus.github.io/modello/location-tracking.html]
> adding this information as comment on every line of generated XML would ease
> tracking for end users
> This will probably require a Modello enhancement then integration
> (idea found during Devoxx 2018 Maven BoF, since users were missing ways to
> diagnose unexpected result in effective pom)
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
