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

   https://issues.apache.org/jira/browse/HADOOP-19674
   
   ### Description of PR
   
   When we try to create an instance of `JettisonJaxbContext` a 
`JAXBContext.newInstance` call will happen. With my understanding JAXB is 
removed since JDK11 
([source](https://docs.oracle.com/en/java/javase/24/migrate/removed-tools-and-components.html#GUID-11F78105-D735-430D-92DD-6C37958FCBC3))
 and if we would like to access JAXB, then we should explicit include them to 
the jars. So a new **jaxb-runtime** dependency is included in the code base. I 
used test scope where ever it was possible but for example in the 
`MRClientService` the `JAXBContextResolver` is in use, so i left the test scope 
there.
   
   ### How was this patch tested?
   
   Unit tests
   - I created a JDK8 build and run the 
`org.apache.hadoop.yarn.webapp.TestWebApp` test
   - I created a JDK17 build and run the` 
org.apache.hadoop.yarn.webapp.TestWebApp` test
   
   ### For code changes:
   
   - [ ] Does the title or this PR starts 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?
   - [ ] 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)?
   - [ ] If applicable, have you updated the `LICENSE`, `LICENSE-binary`, 
`NOTICE-binary` files?
   
   


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