You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@maven.apache.org by "Sylwester Lachiewicz (Jira)" <ji...@apache.org> on 2020/01/17 12:38:00 UTC

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

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

Sylwester Lachiewicz updated MPIR-302:
--------------------------------------
    Fix Version/s: 3.1.0

> Allow usage of supplemental-model in reports (e.g. dependencies)
> ----------------------------------------------------------------
>
>                 Key: MPIR-302
>                 URL: https://issues.apache.org/jira/browse/MPIR-302
>             Project: Maven Project Info Reports Plugin
>          Issue Type: Improvement
>          Components: dependencies, dependency-management
>    Affects Versions: 2.7
>            Reporter: Grégory Joseph
>            Priority: Major
>              Labels: needs-attention
>             Fix For: 3.1.0
>
>         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
(v8.3.4#803005)