build: move to jspecify for nullability#2182
Merged
maxandersen merged 1 commit intojbangdev:mainfrom Aug 15, 2025
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
in trying to fix #2133 I hit that maveninverse and motd are incompatible on maven deps - so trying to remove motd but then I remove javax.annotations (weirdly enough) and thus thought - lets just move to jspecify rather than more intermediate steps.
these are just annotations and we don't use them rigorously so i don't expect it will be of any issue as not affecting runtime and the null checks are dubious anyway :)
in other words - if the build passes i'll merge it even withot review as i prefer not to have PR with this many changes hanging:)