You are viewing a plain text version of this content. The canonical link for it is here.
Posted to yarn-issues@hadoop.apache.org by "Ray Chiang (JIRA)" <ji...@apache.org> on 2017/08/11 20:58:00 UTC
[jira] [Assigned] (YARN-6996) Discuss license issue with
javax.cache library
[ https://issues.apache.org/jira/browse/YARN-6996?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Ray Chiang reassigned YARN-6996:
--------------------------------
Assignee: Ray Chiang
> Discuss license issue with javax.cache library
> ----------------------------------------------
>
> 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
>
> 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-unsubscribe@hadoop.apache.org
For additional commands, e-mail: yarn-issues-help@hadoop.apache.org