ci: expand JDK test matrix per profile#78
Merged
Conversation
Broaden the build matrix (each JDK is ≥ the profile's maven.compiler.release, so every leg is valid). Local dev default stays JDK 21 (.mise.toml unchanged). - tomcat9 (release 11): JDK 11, 17, 18, 21, 25 - tomcat10 (release 17): JDK 17, 18, 25 - tomcat11 (release 21): JDK 21, 25 Docs (README Build Profiles table + CI/CD prose, CLAUDE.md profile table + CI section) updated to match. The README hero flowchart carries no JDK references, so it needs no change. Verified the new (release, JDK) combinations locally: tomcat9@17, tomcat10@17, tomcat11@21 all BUILD SUCCESS + tests pass; actionlint clean. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Broadens the per-profile CI JDK matrix as requested. Default (local dev) stays JDK 21 —
.mise.tomlunchanged; only the CI matrix legs change.maven.compiler.releaseEvery leg is valid (each JDK ≥ the profile's
releaselevel). 6 → 10 build legs.Docs updated: README Build Profiles table + CI/CD prose, CLAUDE.md profile table + CI section. The hero flowchart has no JDK references, so it's unchanged (considered, not skipped).
Verified locally (the new release/JDK combos): tomcat9@JDK17, tomcat10@JDK17, tomcat11@JDK21 — all BUILD SUCCESS + tests pass;
actionlintclean on the workflow.🤖 Generated with Claude Code