Fix SimpleMailMessage nullability annotations #29139
Closed
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.
Fixes the nullability annotations in
SimpleMailMessage
so theset*(...)
methods have their parameters marked as@Nullable
.These method parameters had no annotations and when
SimpleMailMessage
is used from Kotlin with-Xjsr305=strict
enabled, theset*(...)
methods were treated as being marked@NonNull
. This also meant Kotlin would not see matched pairs of get/set methods asvar
properties, so callingmessage.text = "Text"
would not compile in Kotlin.Adds tests in
SimpleMailMessageJsr305ComplianceTests.kt
that verify the nullability annotations forSimpleMailMessage
are correct. This file will actually fail to compile if the nullability annotations are missing, causing the tests to fail.Also modifies
spring-context-support.gradle
to force the Kotlin test code to compile with-Xjsr305=strict
, enabling the test code to work properly.