Skip to content

Build on JDK 25 while keeping the Java 11 bytecode target - #40

Merged
vpaturet merged 1 commit into
masterfrom
ci/build-on-jdk25
Oct 12, 2026
Merged

vpaturet merged 1 commit into
masterfrom
ci/build-on-jdk25

Conversation

@vpaturet

Copy link
Copy Markdown
Contributor

Summary

  • Switch CI to JDK 25: the build job in push.yml, the CodeQL scan, and the shared gha-maven-central release job (which otherwise defaults to JDK 21).
  • Keep the Java 11 target: the compiler plugin already uses <release>${jdk.version}</release> with jdk.version=11, so the published artifact remains usable on Java 11. A pom comment and a CLAUDE.md note document this split.

Builds on #39, which made code generation and SIRI 2.1 validation work on JDK 24+.

Verification

  • mvn clean verify -Ppublication on JDK 25: BUILD SUCCESS, 14 tests pass, javadoc and sources jars produced.
  • All 2184 classes in the built jar are class-file version 55 (Java 11).
  • mvn test on JDK 11 still passes the same 14 tests.

Switch the build, CodeQL and Maven Central release workflows to JDK 25.
The compiler plugin keeps <release>11</release>, so the published artifact
stays usable on Java 11.
@vpaturet vpaturet changed the title ci: build on JDK 25 while keeping the Java 11 bytecode target Build on JDK 25 while keeping the Java 11 bytecode target Oct 12, 2026
@vpaturet
vpaturet merged commit d9b046a into master Oct 12, 2026
2 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant