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


##########
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:
   From my perspective, I haven't noticed any significant compatibility issues 
so far, as Jersey 2.46 should be able to compile without issues on JDK 8, JDK 
11, and JDK 17. I tried compiling the trunk code with JDK 17, and everything 
worked fine. Of course, if we plan to release the first version officially 
supporting JDK 17, there is still some additional work to be done. The biggest 
task right now is upgrading from JUnit 4 to JUnit 5, and my colleague and I are 
working on this together. He has developed an automated code conversion tool 
that can greatly improve the efficiency of the upgrade. I'm currently 
coordinating with him to verify the details, and once everything is confirmed, 
we can accelerate the migration from JUnit 4 to JUnit 5.



-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]


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

Reply via email to