[jira] [Commented] (YARN-6996) Change javax.cache library implementation from JSR107 to Apache Geronimo
[
https://issues.apache.org/jira/browse/YARN-6996?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16127671#comment-16127671
]
Ray Chiang commented on YARN-6996:
--
Thanks [~subru] and [~busbey]!
> 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
>Priority: Blocker
> Fix For: 3.0.0-beta1
>
> Attachments: YARN-6996.001.patch
>
>
> With YARN Federation, we added YARN-3672, which adds the following to
> {noformat}
> javax.cache
> cache-api
> {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
[jira] [Commented] (YARN-6996) Change javax.cache library implementation from JSR107 to Apache Geronimo
[
https://issues.apache.org/jira/browse/YARN-6996?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16126231#comment-16126231
]
Hudson commented on YARN-6996:
--
SUCCESS: Integrated in Jenkins build Hadoop-trunk-Commit #12179 (See
[https://builds.apache.org/job/Hadoop-trunk-Commit/12179/])
YARN-6996. Change javax.cache library implementation from JSR107 to (subru: rev
18f3603bce37e0e07c9075811b1179afc2c227eb)
* (edit)
hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-common/pom.xml
* (edit) hadoop-project/pom.xml
> 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
>Priority: Blocker
> Fix For: 3.0.0-beta1
>
> Attachments: YARN-6996.001.patch
>
>
> With YARN Federation, we added YARN-3672, which adds the following to
> {noformat}
> javax.cache
> cache-api
> {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
[jira] [Commented] (YARN-6996) Change javax.cache library implementation from JSR107 to Apache Geronimo
[
https://issues.apache.org/jira/browse/YARN-6996?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16124298#comment-16124298
]
Sean Busbey commented on YARN-6996:
---
+1 (non-binding) on patch as-is then.
> 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}
> javax.cache
> cache-api
> {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
[jira] [Commented] (YARN-6996) Change javax.cache library implementation from JSR107 to Apache Geronimo
[
https://issues.apache.org/jira/browse/YARN-6996?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=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}
> javax.cache
> cache-api
> {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
[jira] [Commented] (YARN-6996) Change javax.cache library implementation from JSR107 to Apache Geronimo
[
https://issues.apache.org/jira/browse/YARN-6996?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16124179#comment-16124179
]
Subru Krishnan commented on YARN-6996:
--
Thanks [~rchiang] for bringing this up. We had looked at jsr
[license|https://github.com/jsr107/jsr107spec/blob/master/LICENSE.txt] and
looks like even though they have Apache 2.0, they have not updated their
release yet.
The patch itself LGTM, only a minor comment (as [~busbey] pointed out) - we
need to update the Hadoop LICENSE.txt accordingly.
> 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}
> javax.cache
> cache-api
> {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
[jira] [Commented] (YARN-6996) Change javax.cache library implementation from JSR107 to Apache Geronimo
[
https://issues.apache.org/jira/browse/YARN-6996?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16124162#comment-16124162
]
Ray Chiang commented on YARN-6996:
--
Compiling works. Unit test that tests the class that uses the jcache library
passes.
> 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}
> javax.cache
> cache-api
> {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
[jira] [Commented] (YARN-6996) Change javax.cache library implementation from JSR107 to Apache Geronimo
[
https://issues.apache.org/jira/browse/YARN-6996?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16124152#comment-16124152
]
Hadoop QA commented on YARN-6996:
-
| (x) *{color:red}-1 overall{color}* |
\\
\\
|| Vote || Subsystem || Runtime || Comment ||
| {color:blue}0{color} | {color:blue} reexec {color} | {color:blue} 0m
19s{color} | {color:blue} Docker mode activated. {color} |
|| || || || {color:brown} Prechecks {color} ||
| {color:green}+1{color} | {color:green} @author {color} | {color:green} 0m
0s{color} | {color:green} The patch does not contain any @author tags. {color} |
| {color:red}-1{color} | {color:red} test4tests {color} | {color:red} 0m
0s{color} | {color:red} The patch doesn't appear to include any new or modified
tests. Please justify why no new tests are needed for this patch. Also please
list what manual steps were performed to verify this patch. {color} |
|| || || || {color:brown} trunk Compile Tests {color} ||
| {color:blue}0{color} | {color:blue} mvndep {color} | {color:blue} 0m
28s{color} | {color:blue} Maven dependency ordering for branch {color} |
| {color:green}+1{color} | {color:green} mvninstall {color} | {color:green} 15m
59s{color} | {color:green} trunk passed {color} |
| {color:green}+1{color} | {color:green} compile {color} | {color:green} 15m
34s{color} | {color:green} trunk passed {color} |
| {color:green}+1{color} | {color:green} mvnsite {color} | {color:green} 0m
45s{color} | {color:green} trunk passed {color} |
| {color:green}+1{color} | {color:green} javadoc {color} | {color:green} 0m
35s{color} | {color:green} trunk passed {color} |
|| || || || {color:brown} Patch Compile Tests {color} ||
| {color:blue}0{color} | {color:blue} mvndep {color} | {color:blue} 0m
18s{color} | {color:blue} Maven dependency ordering for patch {color} |
| {color:green}+1{color} | {color:green} mvninstall {color} | {color:green} 0m
31s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} compile {color} | {color:green} 12m
1s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} javac {color} | {color:green} 12m
1s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} mvnsite {color} | {color:green} 0m
44s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} whitespace {color} | {color:green} 0m
0s{color} | {color:green} The patch has no whitespace issues. {color} |
| {color:green}+1{color} | {color:green} xml {color} | {color:green} 0m
3s{color} | {color:green} The patch has no ill-formed XML file. {color} |
| {color:green}+1{color} | {color:green} javadoc {color} | {color:green} 0m
35s{color} | {color:green} the patch passed {color} |
|| || || || {color:brown} Other Tests {color} ||
| {color:green}+1{color} | {color:green} unit {color} | {color:green} 0m
13s{color} | {color:green} hadoop-project in the patch passed. {color} |
| {color:green}+1{color} | {color:green} unit {color} | {color:green} 1m
37s{color} | {color:green} hadoop-yarn-server-common in the patch passed.
{color} |
| {color:green}+1{color} | {color:green} asflicense {color} | {color:green} 0m
30s{color} | {color:green} The patch does not generate ASF License warnings.
{color} |
| {color:black}{color} | {color:black} {color} | {color:black} 51m 26s{color} |
{color:black} {color} |
\\
\\
|| Subsystem || Report/Notes ||
| Docker | Image:yetus/hadoop:14b5c93 |
| JIRA Issue | YARN-6996 |
| JIRA Patch URL |
https://issues.apache.org/jira/secure/attachment/12881543/YARN-6996.001.patch |
| Optional Tests | asflicense compile javac javadoc mvninstall mvnsite
unit xml |
| uname | Linux aff4e8ca0768 4.4.0-43-generic #63-Ubuntu SMP Wed Oct 12
13:48:03 UTC 2016 x86_64 x86_64 x86_64 GNU/Linux |
| Build tool | maven |
| Personality | /testptch/hadoop/patchprocess/precommit/personality/provided.sh
|
| git revision | trunk / bbbf0e2 |
| Default Java | 1.8.0_144 |
| Test Results |
https://builds.apache.org/job/PreCommit-YARN-Build/16860/testReport/ |
| modules | C: hadoop-project
hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-common U:
. |
| Console output |
https://builds.apache.org/job/PreCommit-YARN-Build/16860/console |
| Powered by | Apache Yetus 0.6.0-SNAPSHOT http://yetus.apache.org |
This message was automatically generated.
> 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
[jira] [Commented] (YARN-6996) Change javax.cache library implementation from JSR107 to Apache Geronimo
[
https://issues.apache.org/jira/browse/YARN-6996?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16124147#comment-16124147
]
Sean Busbey commented on YARN-6996:
---
patch looks reasonable, presuming compiling works.
is there no license / notice change to back out when moving to the Geronimo jar?
> 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}
> javax.cache
> cache-api
> {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
