[ 
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 for more on RAT.

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

rat flags EPL-1.0 and CDDL-* license files under licenses/binary-release as 
issues.  Note, these license files apply only to 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.


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:I believe RAT also verifies the source bundle doesn't contain binaries.  
See the RM Guide for more on RAT.


> 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 for more on RAT.
> $ cd <edgent-root>
> $ java -jar ~/Downloads/apache-rat-0.12/apache-rat-0.12.jar . >rat.output
> rat flags EPL-1.0 and CDDL-* license files under licenses/binary-release as 
> issues.  Note, these license files apply only to 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.
> 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)

Reply via email to