MultipartProperties moved around in ServletMapping #1520
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.
https://github.com/spring-projects/spring-boot/commits/decc32dde3c04c980466f6f5bc7b25f17ca99c69/spring-boot-project/spring-boot-servlet/src/main/java/org/springframework/boot/servlet/autoconfigure/MultipartProperties.java?browsing_rename_history=true&new_path=module/spring-boot-servlet/src/main/java/org/springframework/boot/servlet/autoconfigure/MultipartProperties.java&original_branch=0b601118bdc3c35d161c9ae58e25d9b104609a65
They moved this around per the spring framework commit linked. I'm not sure this is the right answer in totality, but... its a start. For instance, its unclear to me how this can exist in BOTH situations of 3.5 compatibility and 4.0 compatibility - maybe some of the conditional-on-class type annotations could alternate between two different possible beans or something?