Repository navigation
build(spring): use native-maven-plugin 1.1.19 - #319
Merged
Merged
Conversation
The 1.1.11 build embeds a reachability metadata snapshot without Netty 4.2.19 coverage, so Spring Boot 4.1.2 native images that use Netty fail at run time. 1.1.19 ships the snapshot that includes that coverage.
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.
Summary
native-maven-pluginfrom 1.1.11 to 1.1.19.217b96f(no Netty 4.2.19 coverage). 1.1.19 embeds snapshotb2d36448, which includes thenetty-common:4.2.19.Finalentry.Verification
scripts/verify-runtime-ci.sh spring --stage native(GraalVM 25.4.4.1): BUILD SUCCESS,/jfoundry/native/readyreturnedready.JAVA_25_HOME=<GraalVM 25> scripts/verify-ci-matrix.sh: BUILD SUCCESS.Could not initialize class io.netty.util.ReferenceCountUtil. Boot 4.1.2 + plugin 1.1.11 still resolves snapshot217b96f.Compatibility
No public API, starter, or configuration-property change. The pin stays in
jfoundry-spring-integration-testspluginManagement, which Dependabot'sjfoundry-maven-patchesgroup already maintains. Remove the explanatory comment only if it becomes stale; the version itself should keep moving with patch updates.Related: oracle/graalvm-reachability-metadata#11228 (fixed by #11313) and spring-projects/spring-boot#52390.