dejan2609 opened a new pull request, #23826:
URL: https://github.com/apache/kafka/pull/23826

   **For audit details see this Jira ticket:** KAFKA-21287
   
   **Rationale:**
   The `licenses/` folder shipped in the Kafka binary distribution has drifted 
from the dependencies it covers: one referenced file is missing, one has the 
wrong license text, four ship for nothing, and several copyright lines are 
stale. 
   CI only compares versions in LICENSE-binary, never the contents of 
`licenses/`.
   
   
   ___
   
   **Changes (prepared with Claude Code):**
   
   - Restore the "Eclipse Distribution License - v 1.0" section that was
     dropped in KAFKA-20555 (#22232): jakarta.activation-api and
     jakarta.xml.bind-api are EDL 1.0, not CDDL. Also list
     jakarta.activation there, replacing the reference to the
     non-existent licenses/jakarta-BSD-3-clause (added in #18359).
   - Move jakarta.servlet-api to EPL 2.0, as declared in its POM. It took
     over the CDDL entry of javax.servlet-api, which is CDDL. Drop the
     now-unused CDDL+GPL-1.1 file.
   - Replace the protobuf-java license text (added in #14833 with generic
     wording) with the upstream Google BSD-3 license.
   - Remove license files for dependencies that are not bundled:
     mock-oauth2-server (test-only, #19938), jsr305 and paranamer (removed
     from LICENSE-binary in #18943 and #18950).
   - Sync classgraph, slf4j, jline, jopt-simple, argparse4j and zstd-jni
     license texts with the upstream tag of the bundled version.
   - Fix the Jersey license in NOTICE-binary: Jersey 3.x is available under
     EPL 2.0 (or GPLv2 with the Classpath Exception), not CDDL, and its
     source moved to eclipse-ee4j/jersey.
   
   Co-Authored-By: Claude Opus 5.5 <[email protected]>


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

Reply via email to