rustyrazorblade commented on PR #101: URL: https://github.com/apache/cassandra-easy-stress/pull/101#issuecomment-5297154076
Pushed one more change (6690b64), reversing the \`-Xjdk-release=21\` approach from the previous commit in favor of a simpler design: the build now targets whatever JDK is actually compiling it (JavaVersion.current()), instead of always forcing JDK 21 bytecode regardless of the build JDK. Rationale: the release-artifact-building CI jobs (\`build\`, \`build-check\`, \`create-test-artifact\`) are already hardcoded to JDK 21 — that's the actual single source of truth for what the shipped artifact requires. Pinning the build script to a fixed "21" independently of that was just a second place that could drift out of sync, the same class of issue already fixed for the jib GC flags. This required two follow-on bumps to actually work: - \`kotlin\` 2.2.20 → 2.4.10 — JDK 25 as an explicit Kotlin compiler target requires Kotlin 2.3.0+; 2.2.20 caps out at JVM_24 and fails outright when asked to target 25. - \`kover\` 0.9.2 → 0.9.9 — 0.9.2 calls an internal Kotlin Gradle plugin API removed in the Kotlin 2.4 line, which broke \`koverXmlReport\`'s configuration entirely once Kotlin was bumped. Verified via \`javap\`: building under JDK 21 now produces class file major version 65 (JDK 21), building under JDK 25 produces major version 69 (JDK 25) — confirmed on both. Full suite (test/ktlintCheck/detekt/distTar/shadowJar/jibDockerBuild/tasks/testAllVersions) re-verified on both JDKs. -- 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]
