Spring Framework 6.0 recipe with migration for Spring Assert
#522
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.
What's changed?
Added a base recipe for migrating to Spring Framework 6.
This is not a complete migration, but can serve as a place to put Spring-related migrations necessary (as opposed to changes related to only Spring Boot).
What's your motivation?
#521
Anything in particular you'd like reviewers to focus on?
I copied the format from the earlier
UpgradeSpringFramework_5_3
.Any additional context
I have tested the changes under
MigrateSpringAssert
in our internal migration and it seems to work fine.I have taken the literal text added from the Spring class and reformatted them a bit.
Ideally, the message contain variable name but that would be a harder change to write automatically.
Usage of this is probably not too common anyway as the functions have been deprecated for a long time.
Checklist