maven-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Vladimir Sitnikov (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (MNG-6677) Ability to declare machine-readable license identifier for project
Date Tue, 11 Jun 2019 20:24:00 GMT

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

Vladimir Sitnikov commented on MNG-6677:
----------------------------------------

{quote}As an alternative, you can reuse the name element to write your SPDX ID. Isn't that
enough for the moment?
{quote}
I tried that, however there are lots of "license variations".
 For instance: [http://jtidy.sourceforge.net/license.html]
 It is not a "standard" license.
 So it is somewhat expected to list that license in pom.xml as
{code:xml}
<license>
  <name>Java HTML Tidy License</name>
  <url>http://jtidy.sourceforge.net/license.html</url>
</license>
{code}
For most of the cases (all?) it would be equivalent to BSD-3-Clause, however it would probably
be incorrect to label the license as just BSD-3-Clause.

That is why I'm inclined that name/url seem to be not that bad, and it would probably make
sense to have a field for "machine-readable effective meaning" of the license.

> 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)

Mime
View raw message