[
https://issues.apache.org/jira/browse/MNG-6677?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16861406#comment-16861406
]
Vladimir Sitnikov commented on MNG-6677:
----------------------------------------
[~michael-o], I have tried to search for the request, and I fail to find one.
I see similar issues like https://issues.apache.org/jira/browse/RAT-251 and
https://issues.apache.org/jira/browse/MPIR-382
Did you have something else in mind?
The fun fact is I came from https://github.com/spdx/tools/issues/192 "Support
normalization of license names" (which is very close to MPIR-382), however for
now it looks like the idea of trying to use "standard ID/URL" in <license> tag
won't fly.
That is why I wonder if a dedicated machine-readable field could appear.
Note: I know that 4.0.0 is here "for ages".
> Ability to declare machine-readable license identifier for project
> ------------------------------------------------------------------
>
> Key: MNG-6677
> URL: https://issues.apache.org/jira/browse/MNG-6677
> Project: Maven
> Issue Type: Improvement
> Components: POM
> Affects Versions: 3.6.1
> Reporter: Vladimir Sitnikov
> Priority: Major
>
> Current model for license is something, yet it is not machine-friendly.
> Developers tend to put random data into
> {{<license><name>...</name><url>...</url>}}, and it is hard to analyze in
> automatic way.
> What if we could use SPDX license identifiers/expressions for license
> information?
> Note: currently POM allows to list multiple <license> tags, and it is not
> clear how they should be treated (and? or?). So a machine-readable field
> should probably allow for AND/OR license expressions.
> So it would be nice if there was a way to declare a machine-readable license
> tag.
> I'm not affiliated with SPDX, however OSGi use those ids:
> https://osgi.org/specification/osgi.core/7.0.0/framework.module.html#framework.module-bundle-license
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
