[
https://jira.codehaus.org/browse/MPIR-302?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=360627#comment-360627
]
Michael Osipov commented on MPIR-302:
-------------------------------------
Can you provide a sample project which depicts the problem?
> Allow usage of supplemental-model in reports (e.g. dependencies)
> ----------------------------------------------------------------
>
> Key: MPIR-302
> URL: https://jira.codehaus.org/browse/MPIR-302
> Project: Maven Project Info Reports Plugin
> Issue Type: Improvement
> Components: dependencies, dependency-management
> Affects Versions: 2.7
> Reporter: Grégory Joseph
>
> The remote-resources plugin allows creating and sharing "supplemental
> models", i.e pom snippets that allow overriding (read "fixing") those from
> the repository. We use this to fix licensing info of some libraries that are
> on central with wrong or inaccurate poms.
> See
> http://maven.apache.org/plugins/maven-remote-resources-plugin/supplemental-models.html
> It would be great if the dependencies reports (and others maybe ?) could make
> use of the same information, such that those generated reports are consistent
> with the resources generated by remote-resources plugin.
--
This message was sent by Atlassian JIRA
(v6.1.6#6162)
