Skip to content

Explain why Spring annotations are migrated to JSpecify#984

Closed
Jenson3210 wants to merge 1 commit intomainfrom
jspecify-description-explain-why
Closed

Explain why Spring annotations are migrated to JSpecify#984
Jenson3210 wants to merge 1 commit intomainfrom
jspecify-description-explain-why

Conversation

@Jenson3210
Copy link
Contributor

@Jenson3210 Jenson3210 commented Feb 16, 2026

Summary

  • Improved MigrateFromSpringFrameworkAnnotations description to explain that Spring Framework 7 adopted JSpecify as its nullability annotation standard
  • Improved MigrateToJSpecify description to mention JSpecify as an industry-wide effort

Customers running Spring Boot 4 migrations were confused about why org.springframework.lang.@Nullable and @NonNull were being changed to org.jspecify.annotations equivalents. The recipe descriptions now explain the "why".

  • Closes moderneinc/customer-requests#1869

Improve recipe descriptions for MigrateToJSpecify and
MigrateFromSpringFrameworkAnnotations to explain that Spring Framework 7
has adopted JSpecify as its nullability annotation standard. Customers
running Spring Boot 4 migrations were confused about why annotation
packages were being changed.

Closes moderneinc/customer-requests#1869
@github-project-automation github-project-automation bot moved this to In Progress in OpenRewrite Feb 16, 2026
@Jenson3210 Jenson3210 closed this Feb 16, 2026
@Jenson3210 Jenson3210 deleted the jspecify-description-explain-why branch February 16, 2026 10:45
@github-project-automation github-project-automation bot moved this from In Progress to Done in OpenRewrite Feb 16, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

Status: Done

Development

Successfully merging this pull request may close these issues.

1 participant