java-null-safety

To enforce null-safety in Java, apply JSpecify annotations like @NullMarked at the package level using package-info.java to establish a default non-null contract across your codebase. You then explicitly mark exceptions using @Nullable and @NonNull.

The best way to make a Java package non-null by default is to apply the @NullMarked annotation within your package-info.java file. This configuration ensures all types default to non-null without needing individual annotations.

To migrate legacy Java code for null-safety, enforce non-null returns and guide transitions to Optional where appropriate. Using JSpecify package-level configuration helps validate these boundaries during migration.

You need @Nullable annotations in a @NullMarked Java package when a method return type or parameter can legitimately be null. Since the package defaults to non-null, @Nullable explicitly flags controlled nullability exceptions.

Yes, you can apply JSpecify null-safety configuration across multiple modules by maintaining consistent package-info.java conventions. This validates non-null returns and controlled nullability boundaries throughout your project.