Skip to content

Enable nullability checking for tests in remaining smoke tests - #51927

Open
xoruddl wants to merge 2 commits into
spring-projects:4.0.xfrom
xoruddl:smoke-test-jersey-nullability
Open

xoruddl wants to merge 2 commits into
spring-projects:4.0.xfrom
xoruddl:smoke-test-jersey-nullability

Conversation

@xoruddl

@xoruddl xoruddl commented Oct 1, 2026

Copy link
Copy Markdown
Contributor

Most smoke tests enable nullability checking for their tests, but the following ones don't:

  • spring-boot-smoke-test-jersey
  • spring-boot-smoke-test-secure-jersey
  • spring-boot-smoke-test-log4j2
  • spring-boot-smoke-test-jackson2-mixed
  • spring-boot-smoke-test-jackson2-only

This is similar to #51861 for module/spring-boot-jersey.

Enabling it for the first four didn't report any NullAway errors. For spring-boot-smoke-test-jackson2-only, it reported 2 errors because the fields of JsonPojo are populated through setters during deserialization and are never initialized. The fields and their accessors are now @Nullable, the same way as SampleDocument in spring-boot-smoke-test-data-couchbase.

spring-boot-smoke-test-ant also doesn't enable it, but its tests aren't in a @NullMarked package, so I've left it out.

The configuration is missing on 4.0.x as well, so I've based this on that branch. ./gradlew check passes locally for all five smoke tests with JDK 26.

…oke tests

Signed-off-by: itaekyung <taeyun1411@gmail.com>
Signed-off-by: itaekyung <taeyun1411@gmail.com>
@spring-projects-issues spring-projects-issues added the status: waiting-for-triage An issue we've not yet triaged label Oct 1, 2026
@philwebb philwebb added type: task A general task and removed status: waiting-for-triage An issue we've not yet triaged labels Oct 1, 2026
@philwebb philwebb added this to the 4.0.x milestone Oct 1, 2026

This branch has not been deployed

No deployments
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

type: task A general task

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants