Verify the plugin on Maven 3.9.0 - #740
Merged
Merged
Conversation
The verify matrix runs current Maven only. One extra matrix entry runs the full build and ITs on Maven 3.9.0, the floor the ASF parent enforces, so API drift against the older 3.9 line is caught before a user hits it.
The project compiles Java 11 sources with maven.compiler.release and nothing switches the JDK; on JDK 8 it only passed because Maven 3.10 binds a compiler plugin that tolerates --release there. Maven 3.9.0 binds 3.10.1, which fails with "invalid flag: --release".
slachiewicz
force-pushed
the
agent/verify-maven-3.9.0
branch
from
September 20, 2026 11:06
71e14a1 to
d55109e
Compare
slachiewicz
marked this pull request as ready for review
September 20, 2026 11:23
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
1 participant
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.
Adds one matrix entry (ubuntu, JDK 8, Maven 3.9.0) to the shared verify workflow so the full build and ITs also run on the oldest Maven the ASF parent allows for building (
minimalMavenBuildVersion3.9). The regular matrix runs current Maven only, so API drift against older releases goes unnoticed until a user hit it. Uses the shared workflow'smatrix-includeinput; no new job definition. Same change as apache/maven-dependency-plugin#1701.First finding of the new job:
auxclasspath-with-java-runtime-11compiles Java 11 sources withmaven.compiler.releaseand nothing switches the JDK, so on a JDK 8 runtime it only passed because Maven 3.10 default-binds compiler-plugin 3.15.0, which tolerates--releaseon javac 8; Maven 3.9.0 binds 3.10.1 and fails withinvalid flag: --release. The IT now declaresinvoker.java.version = 11+, as its siblings do, so it runs where it can compile what it tests.