[
https://issues.apache.org/jira/browse/MPIR-382?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16839744#comment-16839744
]
Vincent Privat commented on MPIR-382:
-------------------------------------
I have created [https://github.com/spdx/license-list-XML/issues/855] to see if
they can sanitize the list. I understand it would not be in the plugin scope to
maintain a list of all possible licenses aliases. It would be better to define
all the aliases in SPDX database, and improve the plugin to either include an
SPDX export, or access it using an API. Another (simpler) option would be to
consider licences which have the same URL as equal, in addition of their name.
All these variants of the Apache 2.0 license have the same URL in common. This
would already improve the report readability without a great effort.
> 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
(v7.6.3#76005)
