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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The upgrade to Log4j 2.25.0 introduces a potentially breaking change that could affect modules using Spring. According to the Log4j 2.25.0 release notes, the
log4j-spring-bootstarter no longer includeslog4j-webas a transitive dependency. If any part of the application relies onlog4j-webfor features like automatic Log4j initialization and de-initialization in a servlet container (viaLog4jServletContainerInitializer), this dependency will need to be added explicitly to the relevant module'spom.xmlto prevent runtime issues.