#19 Use JSpecify Annotations for Nullability

[andrej-urvantsev]

• Replaces jakarta nullable annotations by Jspecify
• Bumps up gradle wrapper version

[Col-E]

Odd that the CI failed to build. There aren't any proper tests at the moment (just the demo application) but that doesn't fail the build on the current version of Gradle. Is that new default behavior with 9.X? Quick search appears to suggest so: gradle/gradle#33619

[andrej-urvantsev]

Ah, yes, this should do the trick:

tasks.withType(AbstractTestTask).configureEach {
    failOnNoDiscoveredTests = false
}

I'll update PR a bit later.

[philliplbryant]

I apologize for chiming in on this late in the game. I have implemented these changes as well, but I took a slightly different approach. By adding @NullMarked to the module declaration, all fields are @NonNull unless marked with @Nullable (see https://jspecify.dev/docs/applying/).

I ran into an administrative issue with my employer that is delaying me from creating a pull request with those changes. I'd be happy to share the work if you prefer this approach and you're willing to wait a few more days while I work to resolve the admin issue with my employer?

[andrej-urvantsev]

Up to @Col-E to decide I guess. I took very simple approach - drop in replacement, which should be easy to review.

[andrej-urvantsev]

Closing in favor of #29