[
https://issues.apache.org/jira/browse/NIFI-2991?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15651534#comment-15651534
]
Sean Busbey commented on NIFI-2991:
-----------------------------------
for nifi-standard-nar can we switch to simple-json or the apache project that
does json parsing?
Does twitter4j have an issue tracker? maybe the fastest path is to get them to
use something else for json parsing.
For hive, I think oozie and spark are just excluding the json dependency,
possibly with a note about how folks can make it work "as an optional runtime
need". I haven't checked to see what the hive JIRA is for solving things,
though I've seen a few folks say they'd go make one.
> JSON.org license is now CatX
> ----------------------------
>
> Key: NIFI-2991
> URL: https://issues.apache.org/jira/browse/NIFI-2991
> Project: Apache NiFi
> Issue Type: Bug
> Reporter: Sean Busbey
> Assignee: Joseph Witt
> Priority: Blocker
> Fix For: 1.1.0
>
>
> per [update resolved legal|http://www.apache.org/legal/resolved.html#json]:
> {quote}
> CAN APACHE PRODUCTS INCLUDE WORKS LICENSED UNDER THE JSON LICENSE?
> No. As of 2016-11-03 this has been moved to the 'Category X' license list.
> Prior to this, use of the JSON Java library was allowed. See Debian's page
> for a list of alternatives.
> {quote}
> I don't know how many of our versions include stuff under this license, it's
> definitely currently in master.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
