Add AOT runtime hints for Log4j Core 2 #46410
Open
+151
−12
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 change introduces AOT runtime hints for Log4j Core 2 to support its integration with Spring Boot native images.
Starting with version
2.25.0
, Log4j Core 2 includes built-in GraalVM reachability metadata, allowing native image generation without requiring additional manual configuration.This contribution complements that by adding Spring Boot–specific metadata:
ClassUtils.isPresent(...)
checks.Fixes #42273.
Note
This change should be reviewed in conjunction with #46334, which configures Log4j Core’s
GraalVmProcessor
to generate reachability metadata for Spring Boot’s custom Log4j plugins.