You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@edgent.apache.org by "Dale LaBossiere (JIRA)" <ji...@apache.org> on 2018/01/02 18:22:02 UTC
[jira] [Resolved] (EDGENT-418) Think LICENSE/NOTICE in binary
release .jar & .war are wrong
[ https://issues.apache.org/jira/browse/EDGENT-418?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Dale LaBossiere resolved EDGENT-418.
------------------------------------
Resolution: Fixed
Fix Version/s: Apache Edgent 1.2.0
> 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
> Assignee: Dale LaBossiere
> Priority: Critical
> Fix For: Apache Edgent 1.2.0
>
>
> 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.4.14#64029)