joseluisll opened a new pull request, #8892:
URL: https://github.com/apache/hadoop/pull/8892

   ### Description of PR
   
   Part of HADOOP-19912 (Jetty 12 on ee8): split out of #8699, where it was 
reviewed.
   
   `JerseyTest` moves from `jersey-test-framework-provider-jetty` to 
`jersey-test-framework-provider-jdk-http`, which runs on the JDK's built-in 
HTTP server and needs no third-party server (review on #8699: neither grizzly2 
nor simple). Jersey 2 has no container for Jetty 12, so this has to land before 
the Jetty 12 upgrade. Production HTTP is untouched: `HttpServer2` stays on 
Jetty 9.4.
   
   - hadoop-project: manage `provider-jdk-http` in place of `provider-jetty`, 
keeping the `javax.servlet-api` exclusion.
   - Module poms: switch the artifactId.
   - hadoop-client-minicluster: bundle the jdk-http provider, and do not 
relocate the JDK's `com/sun/net/httpserver` classes. `jetty-util` used to 
arrive only through `provider-jetty`, so it is now declared directly 
(optional), keeping it in the minicluster jar. `hadoop-client-runtime` is 
untouched, so it still ships no `jetty-util` (YARN-11793).
   - LICENSE-binary: replace the provider entry, and add 
`jersey-container-jdk-http`, which the provider brings and minicluster bundles.
   
   ### How was this patch tested?
   
   - The Jersey-based tests ran on the jdk-http provider in the fork's CI. The 
only failure was `TestSSLHttpServerMTLS`, a known intermittent failure 
(HADOOP-19997) unrelated to this change.
   - In the built jars, `hadoop-client-runtime` has 0 `org/eclipse/jetty/util` 
classes and `hadoop-client-minicluster` keeps its relocated `jetty-util` 
classes.
   
   ### For code changes:
   
   - [x] Does the title of this PR start with the corresponding JIRA issue id 
(e.g. 'HADOOP-17799. Your PR title ...')?
   - [ ] Object storage: Have the integration tests been executed and the 
endpoint declared according to the connector-specific documentation? (not 
applicable)
   - [x] If adding new dependencies to the code, are these dependencies 
licensed in a way that is compatible for inclusion under [ASF 
2.0](http://www.apache.org/legal/resolved.html#category-a)? (Jersey jdk-http 
provider and container: same licence as the other Jersey artifacts)
   - [x] If applicable, have you updated the `LICENSE`, `LICENSE-binary`, 
`NOTICE-binary` files?
   
   ### AI Tooling
   
   If an AI tool was used:
   
   - [x] The PR includes the phrase "Contains content generated by <tool>" 
where <tool> is the name of the AI tool used.
   - [x] My use of AI contributions follows the ASF legal policy 
https://www.apache.org/legal/generative-tooling.html
   
   Contains content generated by Claude Code.
   


-- 
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