[
https://issues.apache.org/jira/browse/NIFI-2991?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15651551#comment-15651551
]
Joseph Witt commented on NIFI-2991:
-----------------------------------
for the standard nar yeah the plan is to just revert that commit, reopen the
ticket, and have that new component reworked to use a non problematic license
of which there are plenty of optons now it seems including apache johnzon
apparently.
for twitter4j I do agree that filing an issue/request there is appropriate.
I'll try to remember to do that as part of this.
For hive, that is a good point as I don't actually know the role of the json
dependency. This could be a good approach for now as well.
thanks!
> 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)
