[1402] Use Spring framework BOM to manage Spring and Spring Security dependencies #1403
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.
As part of the preparation work for the "GeoServer 3" migration to Spring 6, we'll use Maven Bill of Materials for dependency sets that provide them (e.g. the new GeoTools BOM will include BOMs for log4j, slf4j, and jackson).
For server projects, we're adding each individual spring and spring-security dependency, either to the root pom's dependencyManagement or in individual modules.
In order to centralize version management for all spring and spring-security dependencies and reduce boilerplate, we'll adopt the spring-framework-bom and spring-security-bom BOMs.
Fixes #1402