Adopt `JSpecify` for nullness

Open
#2,579 7 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
15/100
Issue type
Feature
Clarity
Needs clarification
Activity status
Stale
Tech stack
java
Domain
tooling

Research direction

No files, tests, or entry points are named. First clarify whether the requested change is adopting JSpecify for nullness or migrating javax to jakarta, then locate the affected Java code and dependencies; done should be defined by the selected migration and its validation.

Written by the indexing model from the issue text.

Description

Since javax is deprecated. We should migrate from javax to jakarta.

This is not necessary. But I'd love to contribute if you want. :)

Dominant language
Java
Stars
5.7k
Forks
560
Avg merge
1d 13h
Merged PRs (30d)
43

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from diffplug/spotless

All issues in diffplug/spotless

Similar issues

More Java issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.