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

Dale LaBossiere commented on EDGENT-418:
----------------------------------------

Duh, right, regarding the JAR files.  They only contain Edgent code in them, 
hence require the std AL-v2.0 LICENSE, and either a std NOTICE or, for jars 
that included original pre-apache-contrib code, the "includes IBM 
contributions" NOTICE.  I think these are all set.

Only the WAR contains non-Edgent components.  Its (std/vanilla) LICENSE is 
incorrect.  It needs the declarations that are present in the 
{{binary-release/LICENSE}} for {{console.war}}.  The NOTICE is correct.

Suggest creating a new {{binary-release/console-war-license}} file that 
consists of the right stuff and adjusting build.gradle to utilize it.

> Think LICENSE/NOTICE in binary release .jar & .war are wrong
> ------------------------------------------------------------
>
>                 Key: EDGENT-418
>                 URL: https://issues.apache.org/jira/browse/EDGENT-418
>             Project: Edgent
>          Issue Type: Bug
>          Components: Miscellaneous
>            Reporter: Dale LaBossiere
>            Priority: Critical
>
> An email thread on LICENSE/NOTICE in a .war on general@incubator got me 
> thinking/checking re Edgent.
> The Edgent binary release bundle (.tgz) has a custom/appropriate LICENSE and 
> NOTICE file.
> The Edgent binary release .jar/.war artifacts only have pretty much stock 
> LICENSE & NOTICE files in them.  That seems incorrect.  (it's not clear to me 
> if we can just use the same binary-bundle's LICENSE/NOTICE in each .jar/.war 
> or if each one has to have customization for that particular artifact.  I 
> hope it's the former (common ones for all binary artifacts).
> Today these artifacts are only released as part of the binary-bundle so at 
> least it has the correct info at the top level.  But in the hopefully near 
> future we will also be publishing on maven-central and then it seems even 
> more important to get .jar/.war contents correct.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

Reply via email to