hadoop-common-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Ted Dunning (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HADOOP-13794) JSON.org license is now CatX
Date Mon, 21 Nov 2016 21:48:58 GMT

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

Ted Dunning commented on HADOOP-13794:
--------------------------------------


That artifact should be *very* compatible.  Except where it isn't.

By that I mean that it should have limited coverage, but good fidelity where it has coverage.
Almost all users of the json library use nothing more than JSON{Object,Array,Exception,Tokener,Stringer}.
That is all there.

The json library from json.org has added things like JSONML (I think that is XML support),
JSONWriter and a few other things.

That said, if you can say what you need, we can get it in very quickly. My only constraint
on updates is that I want all code contributors to 

a) stay clean, don't copy the problem library even accidentally

b) agree to the Apache license (essentially like the Apache ICLA).



> JSON.org license is now CatX
> ----------------------------
>
>                 Key: HADOOP-13794
>                 URL: https://issues.apache.org/jira/browse/HADOOP-13794
>             Project: Hadoop Common
>          Issue Type: Bug
>    Affects Versions: 2.8.0, 2.7.4, 3.0.0-alpha2, 2.6.6
>            Reporter: Sean Busbey
>            Priority: Blocker
>
> 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}
> We have a test-time transitive dependency on the {{org.json:json}} artifact in trunk
and branch-2. AFAICT, this test time dependency doesn't get exposed to downstream at all (I
checked assemblies and test-jar artifacts we publish to maven), so it can be removed or kept
at our leisure. keeping it risks it being promoted out of test scope by maven without us noticing.
We might be able to add an enforcer rule to check for this.
> We also distribute it in bundled form through our use of the AWS Java SDK artifacts in
trunk and branch-2. Looking at the github project, [their dependency on JSON.org was removed
in 1.11|https://github.com/aws/aws-sdk-java/pull/417], so if we upgrade to 1.11.0+ we should
be good to go. (this might be hard in branch-2.6 and branch-2.7 where we're on 1.7.4)



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

---------------------------------------------------------------------
To unsubscribe, e-mail: common-issues-unsubscribe@hadoop.apache.org
For additional commands, e-mail: common-issues-help@hadoop.apache.org


Mime
View raw message