Juergen Hoeller opened SPR-15720 and commented
After the measures in #20099, we have consistent @Nullable declarations at the method parameter and return type level already. It turns out that @Nullable at the field level is an essential companion, avoiding mismatches between methods and the fields that they access.
Also, Eclipse only supports "full" nullability through annotations: that is, it doesn't differentiate between parameter level and field level. Extending our @NonNullApi / @Nullable semantics to the field level makes it easier to set those up for Eclipse as well.
Affects: 5.0 RC2
Issue Links:
Referenced from: commits 46eba3d, 9fc4fb1, 00f4c36, c292a89, 301e2ea, cc74a28, 57f961e
Juergen Hoeller opened SPR-15720 and commented
After the measures in #20099, we have consistent
@Nullabledeclarations at the method parameter and return type level already. It turns out that@Nullableat the field level is an essential companion, avoiding mismatches between methods and the fields that they access.Also, Eclipse only supports "full" nullability through annotations: that is, it doesn't differentiate between parameter level and field level. Extending our
@NonNullApi/@Nullablesemantics to the field level makes it easier to set those up for Eclipse as well.Affects: 5.0 RC2
Issue Links:
Referenced from: commits 46eba3d, 9fc4fb1, 00f4c36, c292a89, 301e2ea, cc74a28, 57f961e