aboutcode-org / aboutcode-org/scancode-toolkit

Enhance Request for Java's JCP-based license

Ouverte
#1,510 8 commentaires 1 réaction 1 personne assignée Réclamée par @DennisClark Voir sur GitHub
license scan new feature
Langage dominant
Python
Étoiles
2.6k
Forks
791
Merge moyen
1 j 12 h
PR mergées (30 j)
5

Description

### Description
Since Java 10, the java library is changing from * .jar format to * .mod format, the license is also changing.
Popular licenses for the java library are:
* CDDL-1.1 + GPL-2.0 with ClassPath Exception ,
spdx/Apache-2.0 , spdx/CPL-1.0, spdx/OSL-2.1,spdx/SISSL-1.2,spdx/SPL-1.0, spdx/SPL(Sun Public License),
SCSL(Sun Community Source License=scancode-toolkit/src/licensedcode/data/licenses/scsl-3.0.LICENSE)

Projects that collect a large number of license names for each artifact ID, such as Black Duck, are at an increased risk of incorrectly displaying Java library license names, such as the latest version of the license that replaces Apache-2.0.

The license to be revised in the Java JCP process is Based on several types of templates, various variations are made.
In my analysis, I think that there are probably six types of templates.
However, the appropriate number of classifications depends on the expressive power of scanCode-ToolKit's RULE-engine.

* Java-BCL(Oracle Binary Code License Agreement)
* Java-RL(Java Research License)
* Java-DL(Java Distribution License)
* Java-Spec-Eval(JSR Spec Evaluation License
* Java-Spec-RI(JSR Specification Reference Implementation License Agreement)
(JSR 349 Bbean Validation 1.1 Final Release Spec Evaluation License)
* Java-Spec-doc(java documentated Specification License)
(JavaSE10 spec license-4417634,JavaSE8 spec license-2158700,JavaSE9 spec license-3903847,JavaSE10 spec license-4417634,license template for implementing final JSRs)

It is my essential request to transform the habit of using the name of the work as the license name to the template name of the license text.
As a means of doing this, rather than adding a lot of * .RULE files, I would like to improve the matching ability of the RULE engine to suppress the explosion of * .Rule files.

### System configuration

The above original text can be downloaded from the link below.
* Spec Leads License Reference
https://jcp.org/en/resources/license_reference

* JSRs: Java Specification Requests List of all JSRs
https://jcp.org/en/jsr/all

* Java(TM) Telephony API (JTAPI) Specification 1.4 Final Release 2
https://download.oracle.com/otndocs/jcp/7035-jtapi-1.4-fr2-spec-oth-JSpec/

https://download.oracle.com/otndocs/jcp/7035-jtapi-1.4-fr2-spec-oth-JSpec/7035-jtapi-1.4-fr2-spec-oth-JSpec-license.html

* Java Distribution License
* JSR-925 JavaBeans(TM) Activation Framework Specification ("Specification") Version: 1.2 LIMITED LICENSE GRANTS
  https://download.oracle.com/otn-pub/jcp/jaf-1_2-mrel2-eval-spec/JAF-1.2.pdf?AuthParam=1554636818_3dad69b54b9a49cf1fe9f593094d1980

Guide de contribution

Ouvrir le guide de contribution

Évaluation

Cette issue n'a pas encore été évaluée.

Recevez les nouvelles issues par e-mail

Un résumé court des issues GitHub adaptées aux débutants.