feat: Honor compiler release for Groovy bytecode - #389
Merged
Conversation
Use maven.compiler.release to infer the Groovy target bytecode when targetBytecode is not configured directly. Fall back to maven.compiler.target and then the existing 1.8 default so Groovy classfiles match the Java compiler configuration. Co-Authored-By: Codex <noreply@openai.com>
keeganwitt
force-pushed
the
feat/honor-compiler-release
branch
from
June 25, 2026 05:48
a6b1fe0 to
3d29b11
Compare
keeganwitt
marked this pull request as ready for review
June 25, 2026 05:49
vpelikh
approved these changes
Jun 25, 2026
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
2 participants
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.
Honor
maven.compiler.releasewhen deriving Groovy bytecode target configuration.When
targetBytecodeis not configured directly, compile and stub generation now prefermaven.compiler.release, then fall back tomaven.compiler.target, and finally the existing1.8default. This keeps Groovy classfile output aligned with Maven Compiler Plugin release-based Java builds without treating GroovyDoc as a bytecode-producing path.Version Bump
Bump the plugin snapshot version to
5.1.0-SNAPSHOTfor this behavior change.Fixes #387