spring-projects / spring-projects/spring-batch-extensions
Introduce JSpecify annotations for nullability constraints
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 277
- Forks
- 269
- PR merge metrics
- No merged PRs in 30d
Description
Following spring-projects/spring-framework#28797 and spring-projects/spring-batch#4673, all the extension modules currently on the latest Spring Batch version could adopt JSpecify annotations to ensure build-time validation via NullAway.
See also:
- https://spring.io/blog/2025/03/10/null-safety-in-spring-apps-with-jspecify-and-null-away
- https://docs.openrewrite.org/recipes/java/jspecify/migratefromspringframeworkannotations
-
spring-batch-bigquery -
spring-batch-elasticsearch -
spring-batch-excel -
spring-batch-neo4j -
spring-batch-notion(#191)
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Review the unchecked extension modules: spring-batch-bigquery, spring-batch-elasticsearch, spring-batch-excel, and spring-batch-neo4j. Start with the linked Spring Framework and Spring Batch issues, the JSpecify migration recipe, and the NullAway references; the work is done when those modules adopt the requested annotations and support build-time nullability validation.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- tooling
- Issue type
- Refactor
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 48/100