[jira] [Commented] (JENA-1703) Slim Fuseki combined artifacts NOTICE inclusions.

["A. Soroka (JIRA)" <ji...@apache.org>]

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

A. Soroka commented on JENA-1703:
---------------------------------

[~andy.seaborne] am I correct in understanding that one thing you are doing here is moving all such material into the modules that build actual deployable artifacts (as opposed to {{jena-fuseki2}}, {{jena-fuseki-core}}, etc.)?

> Slim Fuseki combined artifacts NOTICE inclusions.
> -------------------------------------------------
>
>                 Key: JENA-1703
>                 URL: https://issues.apache.org/jira/browse/JENA-1703
>             Project: Apache Jena
>          Issue Type: Task
>    Affects Versions: Jena 3.10.0
>            Reporter: Andy Seaborne
>            Assignee: Andy Seaborne
>            Priority: Major
>             Fix For: Jena 3.11.0
>
>          Time Spent: 40m
>  Remaining Estimate: 0h
>
> The current jena-fuseki2 LICENSE and NOTICE setup is putting more than is necessary. A combined NOTICE (which ends up being called `meta-inf/notice` after the shader transformer has run) should only have required content (e.g. acknwledgement for bianaries, especially forBSD and MIT with links to the license).
> Apache Lucene already produces a suitable "notice" and this gets rolled up automatically (as do other Apache project dependencies). 3rd par ones tend not to have anything in their binary jar files so we ought to put in the required items in NOTICE at the point of shading.
>  



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)