You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Romain Manni-Bucau (Jira)" <ji...@apache.org> on 2021/05/18 07:23:00 UTC

[jira] [Commented] (MNG-6677) Ability to declare machine-readable license identifier for project

    [ https://issues.apache.org/jira/browse/MNG-6677?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17346633#comment-17346633 ] 

Romain Manni-Bucau commented on MNG-6677:
-----------------------------------------

What about these 2 actions:
1. make asf parent using the normalized name
2. add to our xsd completion capability for known licenses (normalized fashion)

this way no breaking change and we still support custom licenses but we enable and encourage normalized values.

> 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
>             Fix For: Issues to be reviewed for 4.x
>
>
> 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
(v8.3.4#803005)