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

ASF subversion and git services commented on NIFI-3825:
-------------------------------------------------------

Commit 829c02b058199bff167b4e78934584cabc92de78 in nifi's branch 
refs/heads/master from [~joewitt]
[ https://git-wip-us.apache.org/repos/asf?p=nifi.git;h=829c02b ]

NIFI-3825 fix L&N for jolt, json, and source deps

Signed-off-by: Scott Aslan <[email protected]>

This closes #1765


> Fix L&N for open json and jolt references
> -----------------------------------------
>
>                 Key: NIFI-3825
>                 URL: https://issues.apache.org/jira/browse/NIFI-3825
>             Project: Apache NiFi
>          Issue Type: Bug
>          Components: Tools and Build
>    Affects Versions: 1.2.0
>            Reporter: Joseph Witt
>            Assignee: Joseph Witt
>            Priority: Critical
>             Fix For: 1.2.0
>
>
> TDUNNING open-json is in at least nifi-gcp-nar and nifi-assembly.  Must be in 
> both NOTICE files.  Needs an entry for it as ASLv2 and its copyright.  As 
> found here: https://github.com/tdunning/open-json/tree/json-1.8
> +++
> Android JSON library
> Copyright (C) 2010 The Android Open Source Project
> This product includes software developed by
> The Android Open Source Project
> JOLT L&N needs to be improved.
> - It is found in the nifi-standard-nar LICENSE file despite being an ASLv2 
> item.  It is already properly in the NOTICE so just needs removal from 
> LICENSE.
> - It is found in the nifi-jolt-transform-json-ui in LICENSE.  Is already in 
> NOTICE properly so just needs removal from LICENSE.
> - We have an apparent source dependency from reading the NOTICE but might 
> have an incorrect header and/or we need to carry that to the top level notice 
> as well.
> standard-bundle-nar has source reference to elastic but it is not in top 
> level notice



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

Reply via email to