Open
Description
More info in the Spring Framework 7.0
docs: https://docs.spring.io/spring-framework/reference/7.0/core/null-safety.html.
We can treat this issue an Epic and have sub-issues for specific tasks or dedicated module fixes.
This can be done in phase:
- Migrate from deprecated
org.springframework.lang.Nullable
on properties methods to theorg.jspecify.annotations.Nullable
. - Migrate
@org.springframework.lang.NonNullApi
and@org.springframework.lang.NonNullFields
pair to the@org.jspecify.annotations.NullMarked
. However this would trigger the third phase. - Fix nullabilty errors in those
@org.jspecify.annotations.NullMarked
packages. - Add more and more
@org.jspecify.annotations.NullMarked
and fix respective nullability vulnerabilities in those package and modules.
Any other thoughts and possible ways to fix this huge task are welcome!