dongjoon-hyun opened a new pull request, #56937:
URL: https://github.com/apache/spark/pull/56937

   ### What changes were proposed in this pull request?
   
   This PR removes the stale `javax.xml.bind:jaxb-api` entry from the "Common 
Development and Distribution License (CDDL) 1.1" section of `LICENSE-binary`.
   
   ### Why are the changes needed?
   
   `LICENSE-binary` documents the third-party dependencies bundled in the Spark 
binary distribution, but `javax.xml.bind:jaxb-api` is no longer shipped:
   
   - The bundled-jar manifest `dev/deps/spark-deps-hadoop-3-hive-2.3` contains 
no `javax.xml.bind:jaxb-api` jar. It only has the Jakarta replacement 
`jakarta.xml.bind-api-4.0.5`, plus `jaxb-core-4.0.6` and `jaxb-runtime-4.0.6`.
   - The only build reference to `javax.xml.bind:jaxb-api` is at `test` scope 
in `resource-managers/yarn/pom.xml` ("Used by MiniYARNCluster"). The root 
`pom.xml` only manages its version in `<dependencyManagement>`; no 
compile/runtime dependency declares it.
   - Test-scope dependencies are not shipped in the binary distribution, so 
this entry does not belong in `LICENSE-binary`. It is a leftover from before 
the `javax` -> `jakarta` JAXB migration.
   
   ### Does this PR introduce _any_ user-facing change?
   
   No.
   
   ### How was this patch tested?
   
   Manual review. `git diff LICENSE-binary` confirms exactly one line is 
removed, leaving the other CDDL 1.1 entries (`javax.transaction:jta`, 
`javax.servlet:javax.servlet-api`) untouched.
   
   ### Was this patch authored or co-authored using generative AI tooling?
   
   Generated-by: Claude Opus 4.8


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