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/03/05 22:05:00 UTC

[jira] [Closed] (MPIR-382) Group different license spellings together

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

Sylwester Lachiewicz closed MPIR-382.
-------------------------------------
    Fix Version/s:     (was: wontfix-candidate)
       Resolution: Won't Fix

> Group different license spellings together
> ------------------------------------------
>
>                 Key: MPIR-382
>                 URL: https://issues.apache.org/jira/browse/MPIR-382
>             Project: Maven Project Info Reports Plugin
>          Issue Type: Improvement
>          Components: licenses
>    Affects Versions: 3.0.0
>            Reporter: Vincent Privat
>            Priority: Major
>
> The licenses report is not aware of the different possible spellings we can find in all Maven dependencies published on Maven Central. This results in any given license (for example, Apache 2.0) being listed several times. For example, take a look to the seven variants listed in [maven-site-plugin dependencies|http://maven.apache.org/plugins/maven-site-plugin/dependencies.html#Licenses]:
>  * Apache Public License 2.0
>  * Apache License Version 2
>  * Apache License, Version 2.0
>  * Apache Software License - Version 2.0
>  * Apache License 2.0
>  * Apache License Version 2.0
>  * The Apache Software License, Version 2.0
> On a large project, this makes the license report unreadable. The plugin should detect all these variants denote the same license and group them together.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)