Mailing-List: contact dev-help@edgent.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@edgent.apache.org
Date: Mon, 14 Nov 2016 18:40:58 +0000 (UTC)
From: "Dale LaBossiere (JIRA)" <jira@apache.org>
To: dev@edgent.incubator.apache.org
Message-ID: <JIRA.13014350.1477075256000.271900.1479148858397@Atlassian.JIRA>
In-Reply-To: <JIRA.13014350.1477075256000@Atlassian.JIRA>
References: <JIRA.13014350.1477075256000@Atlassian.JIRA> <JIRA.13014350.1477075256587@arcas>
Subject: [jira] [Updated] (EDGENT-290) Check licenses via rat
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
archived-at: Mon, 14 Nov 2016 18:41:39 -0000


     [ https://issues.apache.org/jira/browse/EDGENT-290?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Dale LaBossiere updated EDGENT-290:
-----------------------------------
    Description: 
RAT checks source file licensing headers, verifies the source bundle doesn't contain binaries.  
See the RM Guide and/or http://creadur.apache.org/rat/ for more on RAT

$ cd <edgent-root>
$ java -jar ~/Downloads/apache-rat-0.12/apache-rat-0.12.jar . >rat.output

rat flags EDL-*, EPL-* and CDDL-* license files under licenses/binary-release as issues.  Note, these license files apply only to binary content included in a binary-release.  The content is not included in a source release.

The CDDL license files, copied from the associated external content's license info, also contain a GPL-2 license as the content is dual licensed.  CDDL-1.0 and CDDL-1.1 are acceptable for binary-only content [1]
The EPL license files, copied from the associated external contents license info, is acceptable for binary-only content [1].
The EDL license files, copied from the associated external contents license info, also notes EPL-1.0 licensing as the content is dual licensed.  EDL-1.0 is acceptable [2]

[1] http://www.apache.org/legal/resolved.html#category-b
[2] http://www.apache.org/legal/resolved.html#category-a


Can also try http://compliance.rocks on generated source and binary release bundles.
For a binary release you'll have to select a custom configuration to exclude considering bundled binaries as an error.

For a source release image, compliance.rocks acceptable reports only reports files under console/servlets/webapp_content/js/ext as potential issues.  These files are "external content" whose license info is covered in LICENSE.
For a binary release image, compliance.rocks acceptably reports only two generated javadoc files lack licenses.


  was:
RAT checks source file licensing headers, verifies the source bundle doesn't contain binaries.  
See the RM Guide for more on RAT.

$ cd <edgent-root>
$ java -jar ~/Downloads/apache-rat-0.12/apache-rat-0.12.jar . >rat.output

rat flags EDL-*, EPL-* and CDDL-* license files under licenses/binary-release as issues.  Note, these license files apply only to binary content included in a binary-release.  The content is not included in a source release.

The CDDL license files, copied from the associated external content's license info, also contain a GPL-2 license as the content is dual licensed.  CDDL-1.0 and CDDL-1.1 are acceptable for binary-only content [1]
The EPL license files, copied from the associated external contents license info, is acceptable for binary-only content [1].
The EDL license files, copied from the associated external contents license info, also notes EPL-1.0 licensing as the content is dual licensed.  EDL-1.0 is acceptable [2]

[1] http://www.apache.org/legal/resolved.html#category-b
[2] http://www.apache.org/legal/resolved.html#category-a


Can also try http://compliance.rocks on generated source and binary release bundles.
For a binary release you'll have to select a custom configuration to exclude considering bundled binaries as an error.

For a source release image, compliance.rocks acceptable reports only reports files under console/servlets/webapp_content/js/ext as potential issues.  These files are "external content" whose license info is covered in LICENSE.
For a binary release image, compliance.rocks acceptably reports only two generated javadoc files lack licenses.


> Check licenses via rat
> ----------------------
>
>                 Key: EDGENT-290
>                 URL: https://issues.apache.org/jira/browse/EDGENT-290
>             Project: Edgent
>          Issue Type: Sub-task
>            Reporter: Dale LaBossiere
>            Assignee: Dale LaBossiere
>
> RAT checks source file licensing headers, verifies the source bundle doesn't contain binaries.  
> See the RM Guide and/or http://creadur.apache.org/rat/ for more on RAT
> $ cd <edgent-root>
> $ java -jar ~/Downloads/apache-rat-0.12/apache-rat-0.12.jar . >rat.output
> rat flags EDL-*, EPL-* and CDDL-* license files under licenses/binary-release as issues.  Note, these license files apply only to binary content included in a binary-release.  The content is not included in a source release.
> The CDDL license files, copied from the associated external content's license info, also contain a GPL-2 license as the content is dual licensed.  CDDL-1.0 and CDDL-1.1 are acceptable for binary-only content [1]
> The EPL license files, copied from the associated external contents license info, is acceptable for binary-only content [1].
> The EDL license files, copied from the associated external contents license info, also notes EPL-1.0 licensing as the content is dual licensed.  EDL-1.0 is acceptable [2]
> [1] http://www.apache.org/legal/resolved.html#category-b
> [2] http://www.apache.org/legal/resolved.html#category-a
> Can also try http://compliance.rocks on generated source and binary release bundles.
> For a binary release you'll have to select a custom configuration to exclude considering bundled binaries as an error.
> For a source release image, compliance.rocks acceptable reports only reports files under console/servlets/webapp_content/js/ext as potential issues.  These files are "external content" whose license info is covered in LICENSE.
> For a binary release image, compliance.rocks acceptably reports only two generated javadoc files lack licenses.


--
This message was sent by Atlassian JIRA
(v6.3.4#6332)