Inherit the maven-invoker-plugin version from the parent - #435
Merged
Conversation
The local version.maven-invoker-plugin property pinned 3.9.1. That was a bump when it was added, but org.apache:apache:39 now manages 3.10.1, so the property had quietly become a downgrade. It is not only stale. maven-invoker-plugin 3.9.1 brings in Groovy 4.0.27, whose bundled ASM cannot read JDK 26 class files, so every verify.groovy post-build hook dies with "Unsupported class file major version 70" while the integration test's own build.log still reports success. 3.10.1 ships Groovy 4.0.31, which handles JDK 26. Drop the property rather than restate a version the parent already owns. Generated-by: Claude Opus 5 (1M context)
slachiewicz
added
maintenance
dependencies
slachiewicz
marked this pull request as ready for review
August 9, 2026 14:33
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.
The local
version.maven-invoker-pluginproperty pins 3.9.1. That was a bump when it was added, butorg.apache:apache:39— reached through the parent chain — now manages 3.10.1, so the property had quietly turned into a downgrade.It is not just stale. maven-invoker-plugin 3.9.1 brings in Groovy 4.0.27, whose bundled ASM cannot read JDK 26 class files, so on a JDK 26 toolchain every
verify.groovypost-build hook dies with:The failure mode is nastier than a plain failure: the integration test's own
build.logstill ends inBUILD SUCCESSand only the post-build hook blows up, so a broken run and a good one look identical until you read the stack trace. 3.10.1 ships Groovy 4.0.31, which handles JDK 26.So this drops the property rather than restating a version the parent already owns.
mvn help:effective-pomconfirms maven-invoker-plugin resolves to 3.10.1 with the line gone.Part of a sweep across the Maven repositories for local pom properties that no longer override anything useful. The same change in apache/maven-checkstyle-plugin (#685) took its integration tests on JDK 26 from failing in the script interpreter to 49/49 passing.
Generated-by: Claude Opus 5 (1M context)