aglinxinyuan commented on PR #6225: URL: https://github.com/apache/texera/pull/6225#issuecomment-4910091176
jOOQ 3.20+ (Open Source Edition) ships Java 21 bytecode, so 3.21.6 blew up at test runtime on our Java 17 CI matrix with `UnsupportedClassVersionError` — `build / amber-integration` and `build / platform (computing-unit-managing-service)`. Capped at **3.19.36**, the last release that still targets Java 17, across `amber`, `computing-unit-managing-service` and `common/dao`, and resynced the binary license metadata for all seven service dists: - jooq bullet `3.16.23 → 3.19.36` in every `LICENSE-binary` - `amber` drops `com.sun.activation.jakarta.activation` — jOOQ's `jakarta.xml.bind-api` dependency became `optional` in 3.19, so amber's xml.bind-api falls back to 2.3.2 with no transitive activation jar - `NOTICE-binary` regenerated (`io.r2dbc.r2dbc-spi 0.9.0 → 1.0.0` everywhere; amber also reflects the xml.bind-api/activation changes) `jooq-codegen` stays at 3.16.23 — build-time only, not bundled, generated code is forward-compatible with the 3.19 runtime, and the 42.7.4 pgjdbc codegen pin still applies below 3.20. A proper move to 3.21.x would need a project-wide Java 21 migration, which is out of scope for a dependency bump. -- 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]
