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

Subru Krishnan commented on YARN-6996:
--------------------------------------

[~busbey], thanks for validating the fix. Like I mentioned above we assumed the 
jsr 107 license was Apache 2.0 and so we don't need any license / notice change 
to back out when moving to the (Apache) Geronimo.

> Change javax.cache library implementation from JSR107 to Apache Geronimo
> ------------------------------------------------------------------------
>
>                 Key: YARN-6996
>                 URL: https://issues.apache.org/jira/browse/YARN-6996
>             Project: Hadoop YARN
>          Issue Type: Bug
>    Affects Versions: 3.0.0-beta1
>            Reporter: Ray Chiang
>            Assignee: Ray Chiang
>         Attachments: YARN-6996.001.patch
>
>
> With YARN Federation, we added YARN-3672, which adds the following to 
> {noformat}
>     <groupId>javax.cache</groupId>
>     <artifactId>cache-api</artifactId>
> {noformat}
> This third-party library has some murky license history, as documented in 
> this [really long comment 
> thread|https://github.com/jsr107/jsr107spec/issues/333].  The summary of the 
> thread is that "the library is officially APL (take our word for it), but 
> there hasn't been a subsequent release with the license file change".
> LEGAL-325 has been filed to discuss the validity of this license for Apache.
> Before we get to final Hadoop 3 release, I'm wondering if anyone else has 
> concerns about using this library.  Just from looking at the various javax 
> Maven artifacts in our pom.xml files, I see a lot of other javax.* library 
> entries (although we may not ship the .jars if they're part of the Java 
> runtime).



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

---------------------------------------------------------------------
To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org

Reply via email to