edgent-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "John D. Ament (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (EDGENT-418) Think LICENSE/NOTICE in binary release .jar & .war are wrong
Date Tue, 30 May 2017 15:47:04 GMT

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

John D. Ament commented on EDGENT-418:
--------------------------------------

The LICENSE and NOTICE contain information relevant to this package.  If a JAR has transitive
dependencies, those shouldn't be included.  However, if you have an uber jar then that should
include all relevant notices/licenses.

Likewise, since a WAR contains other packages, its NOTICE/LICENSE should represent all of
its contents.

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

Mime
View raw message