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

Robert Kanter commented on OOZIE-2723:
--------------------------------------

I re-checked using maven's dependency:tree instead of just looking at the 
resulting jars, and Pig doesn't actually use JSON.org (I confirmed by looking 
at the Pig repo).  It's hive-common which depends on JSON.org (so it shows up 
in the Pig sharelib and the Hive sharelib).

{quote}Are we essentially blocked on making new Oozie releases until there have 
been releases of those projects?{quote}
That would be really bad.  Oozie hasn't had an actual release in over a year 
and we have a lot of content to get out there.  It would be quite a delay to 
have to wait for a new Hive release.  That said, even if we did this, there's 
nothing stopping a user from overriding the {{hive.version}} during the build 
to an older Hive, and getting JSON.org.  Given that, is this really a 
requirement?  Oozie doesn't have a binary release, so we wouldn't actually be 
shipping anything.  And Oozie itself wouldn't depend on JSON.org.

Otherwise, I guess our only option is to exclude JSON.org and hope nothing 
breaks.  I suppose we could add a release note letting users know that if they 
need JSON.org in the Hive or Hive2 actions, they'll need to add it manually.
https://github.com/apache/hive/search?p=1&q=%22org.json%22&utf8=%E2%9C%93

> JSON.org license is now CatX
> ----------------------------
>
>                 Key: OOZIE-2723
>                 URL: https://issues.apache.org/jira/browse/OOZIE-2723
>             Project: Oozie
>          Issue Type: Bug
>    Affects Versions: 4.3.0
>            Reporter: Sean Busbey
>            Assignee: Robert Kanter
>            Priority: Blocker
>             Fix For: 4.3.0
>
>         Attachments: OOZIE-2723.001.patch
>
>
> 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}
> Looks like this is on branch-4.3 and later. (maybe earlier if it was brought 
> in transitively.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Reply via email to