You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Grégory Joseph (JIRA)" <ji...@codehaus.org> on 2015/03/16 16:09:18 UTC

[jira] (MPIR-302) Allow usage of supplemental-model in reports (e.g. dependencies)

     [ https://jira.codehaus.org/browse/MPIR-302?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Grégory Joseph updated MPIR-302:
--------------------------------

    Attachment: BUILD-185-MPIR-302.zip

Sorry this took a while, but here's an example.

If you run {{mvn clean install site:site}}, you'll see that {{sample/target/classes/README.txt}} contains corrected license information about ASM; this comes from the supplemental-model file.
You'll also see that {{sample/target/site/dependencies.html}} does not. (asm:asm:3.1 has no license info in its pom)

> 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
>         Attachments: BUILD-185-MPIR-302.zip
>
>
> 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)