Exclude spring-boot-devtools from AOT processing in Maven #46533
Conversation
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
Previously, spring-boot-devtools was only excluded from native images built with Gradle but not with Maven. This inconsistency meant that Maven builds would include devtools in the AOT processing classpath, causing the native image to fail or include unnecessary code. This commit applies the existing DEVTOOLS_EXCLUDE_FILTER to the classpath used during both main and test AOT processing in Maven, matching the behavior of the Gradle plugin which excludes the developmentOnly configuration. The exclusion happens automatically without requiring any user configuration, ensuring that devtools is properly excluded from native images while maintaining its functionality during development. Fixes spring-projectsgh-32853 Signed-off-by: academey <[email protected]>
spring-projects-issues
added
the
status: waiting-for-triage
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.
This PR ensures that spring-boot-devtools is excluded from AOT processing when building native images with Maven, matching the existing behavior in Gradle.
Problem:
When building native images with Maven, spring-boot-devtools remains on the classpath during AOT processing. This causes issues because devtools uses features incompatible with native images (like class proxies). In contrast, Gradle automatically excludes devtools through its
developmentOnlyconfiguration.Solution:
DEVTOOLS_EXCLUDE_FILTERto the classpath used during AOT processing in bothProcessAotMojoandProcessTestAotMojoTesting:
Fixes #32853