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

Sean Mackrory commented on HADOOP-15080:
----------------------------------------

Someone can correct me if a higher authority has already clarified this 
differently from me, but my interpretation is that solution 2 is acceptable, 
but solution 1 is not. json-lib is not allowed because of a clause that it only 
be used for "good, not evil", which would seem to me to apply to it's use in 
tests just as much as it would to a distribution. So I think even in test-scope 
we would not be allowed to use it. jersey-json is dual-licensed under CDDL 
(which can be used in binary form for tests, etc.) and GPL (which is also 
category-x), and although I can't find where the authors specify that the 
dual-licensing allows you to abide by either license instead of by both 
licenses, jersey-json is already in use elsewhere in Hadoop so I would assume 
this question has already been settled and we can safely use jersey-json in 
test scope.

So I would vote for solution 2, if we can get that done within a couple of days.

> Cat-X dependency on org.json via derived json-lib
> -------------------------------------------------
>
>                 Key: HADOOP-15080
>                 URL: https://issues.apache.org/jira/browse/HADOOP-15080
>             Project: Hadoop Common
>          Issue Type: Bug
>          Components: fs/oss
>    Affects Versions: 3.0.0-beta1
>            Reporter: Chris Douglas
>            Priority: Blocker
>         Attachments: HADOOP-15080-branch-3.0.0.001.patch
>
>
> The OSS SDK has a dependency on json-lib. In LEGAL-245, the org.json library 
> (from which json-lib may be derived) is released under a 
> [category-x|https://www.apache.org/legal/resolved.html#json] license.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to