[
https://issues.apache.org/jira/browse/MPIR-382?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16864784#comment-16864784
]
Michael Osipov commented on MPIR-382:
-------------------------------------
Refusing to implement this because this fix the symptom not the cause. Request
upsteam to fix their POMs.
> 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
> Fix For: wontfix-candidate
>
>
> 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
(v7.6.3#76005)
