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

ASF GitHub Bot commented on HADOOP-15984:
-----------------------------------------

slfan1989 commented on code in PR #7315:
URL: https://github.com/apache/hadoop/pull/7315#discussion_r1926308234


##########
LICENSE-binary:
##########
@@ -535,6 +525,24 @@ jakarta.ws.rs-api:jakarta.ws.rs-api:2.1.6
 jakarta.servlet.jsp:jakarta.servlet.jsp-api:2.3.6
 jakarta.servlet:jakarta.servlet-api:4.0.4
 
+Eclipse Public License (EPL) 2.0 with some parts being
+GNU General Public License (GPL), Version 2, With Classpath Exception,
+Apache License, 2.0 or Public Domain
+--------------------------
+
+See also https://github.com/eclipse-ee4j/jersey/blob/master/NOTICE.md
+
+org.glassfish.jersey.core:jersey-common:2.46
+org.glassfish.jersey.core:jersey-server:2.46
+org.glassfish.jersey.inject:jersey-hk2:2.46
+org.glassfish.jersey.core:jersey-client:2.46
+org.glassfish.jersey.test-framework:jersey-test-framework-core:2.46
+org.glassfish.jersey.test-framework.providers:jersey-test-framework-provider-grizzly2:2.46
+org.glassfish.jersey.containers:jersey-container-servlet:2.46
+org.glassfish.jersey.containers:jersey-container-servlet-core:2.46
+org.glassfish.jersey.media:jersey-media-json-jettison:2.46
+org.glassfish.jersey.media:jersey-media-jaxb:2.46
+

Review Comment:
   @Hexiaoqiao Thank you for your message. I agree with your point. We will 
keep HADOOP-15984 in the trunk branch and avoid updating it in the active 
branches to continue verifying this change. Once the other features are ready, 
we can discuss the release plan for Hadoop 3.5.0 together. In the meantime, I 
will continue to follow up on the JDK 17 upgrade and the necessary 
improvements, hoping we can successfully achieve our goals.



##########
LICENSE-binary:
##########
@@ -535,6 +525,24 @@ jakarta.ws.rs-api:jakarta.ws.rs-api:2.1.6
 jakarta.servlet.jsp:jakarta.servlet.jsp-api:2.3.6
 jakarta.servlet:jakarta.servlet-api:4.0.4
 
+Eclipse Public License (EPL) 2.0 with some parts being
+GNU General Public License (GPL), Version 2, With Classpath Exception,
+Apache License, 2.0 or Public Domain
+--------------------------
+
+See also https://github.com/eclipse-ee4j/jersey/blob/master/NOTICE.md
+
+org.glassfish.jersey.core:jersey-common:2.46
+org.glassfish.jersey.core:jersey-server:2.46
+org.glassfish.jersey.inject:jersey-hk2:2.46
+org.glassfish.jersey.core:jersey-client:2.46
+org.glassfish.jersey.test-framework:jersey-test-framework-core:2.46
+org.glassfish.jersey.test-framework.providers:jersey-test-framework-provider-grizzly2:2.46
+org.glassfish.jersey.containers:jersey-container-servlet:2.46
+org.glassfish.jersey.containers:jersey-container-servlet-core:2.46
+org.glassfish.jersey.media:jersey-media-json-jettison:2.46
+org.glassfish.jersey.media:jersey-media-jaxb:2.46
+

Review Comment:
   @Hexiaoqiao Thank you for your message! I agree with your point. We will 
keep HADOOP-15984 in the trunk branch and avoid updating it in the active 
branches to continue verifying this change. Once the other features are ready, 
we can discuss the release plan for Hadoop 3.5.0 together. In the meantime, I 
will continue to follow up on the JDK 17 upgrade and the necessary 
improvements, hoping we can successfully achieve our goals.





> Update jersey from 1.19 to 2.x
> ------------------------------
>
>                 Key: HADOOP-15984
>                 URL: https://issues.apache.org/jira/browse/HADOOP-15984
>             Project: Hadoop Common
>          Issue Type: Improvement
>            Reporter: Akira Ajisaka
>            Assignee: Shilun Fan
>            Priority: Major
>              Labels: pull-request-available
>          Time Spent: 2h 10m
>  Remaining Estimate: 0h
>
> jersey-json 1.19 depends on Jackson 1.9.2. Let's upgrade.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

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

Reply via email to