pgjdbc/pgjdbc GitHub issues and pull requests (mirror)help / color / mirror / Atom feed
[pgjdbc/pgjdbc] issue #3634: Migrate nullability annotations from checkerframework to jspecify 4+ messages / 3 participants [nested] [flat]
* [pgjdbc/pgjdbc] issue #3634: Migrate nullability annotations from checkerframework to jspecify @ 2025-05-21 17:50 "vlsi (@vlsi)" <[email protected]> 0 siblings, 0 replies; 4+ messages in thread From: vlsi (@vlsi) @ 2025-05-21 17:50 UTC (permalink / raw) To: pgjdbc/pgjdbc <[email protected]> JSpecify has been released 1.0.0, and Kotlin compiler treats those annotations strictly since 2.1. It makes sense to go for JSpecify nullability annotations. It would probably count as a minor version bump. See https://jspecify.dev/docs/start-here/ ^ permalink raw reply [nested|flat] 4+ messages in thread
* Re: [pgjdbc/pgjdbc] issue #3634: Migrate nullability annotations from checkerframework to jspecify @ 2025-05-31 09:16 ` "vlsi (@vlsi)" <[email protected]> 2 siblings, 0 replies; 4+ messages in thread From: vlsi (@vlsi) @ 2025-05-31 09:16 UTC (permalink / raw) To: pgjdbc/pgjdbc <[email protected]> Guava has recently switched to jspecify: https://github.com/google/guava/releases/tag/v33.4.4 ^ permalink raw reply [nested|flat] 4+ messages in thread
* Re: [pgjdbc/pgjdbc] issue #3634: Migrate nullability annotations from checkerframework to jspecify @ 2025-06-04 19:05 ` "lobaorn-bitso (@lobaorn-bitso)" <[email protected]> 2 siblings, 0 replies; 4+ messages in thread From: lobaorn-bitso (@lobaorn-bitso) @ 2025-06-04 19:05 UTC (permalink / raw) To: pgjdbc/pgjdbc <[email protected]> Hey @vlsi just to add more here, recently JUnit did it as well for 6.0.0-M1. To avoid manual work, I would suggest going in the direction of using OpenRewrite (https://www.moderne.ai/blog/mass-migration-of-nullability-annotations-to-jspecify / https://docs.openrewrite.org/recipes/java/jspecify) for this. Although there is no specific recipe for migrating from CheckerFramework to JSpecify, it should be quite similar to the other ones, using a YAML approach. Other than that, I believe you could use IntelliJ for that to expedite: https://www.jetbrains.com/help/idea/openrewrite.html#create-openrewrite-recipe . If everything goes well with a "recipe" for it could be a opportunity to open a PR for it. cc @timtebeek ^ permalink raw reply [nested|flat] 4+ messages in thread
* Re: [pgjdbc/pgjdbc] issue #3634: Migrate nullability annotations from checkerframework to jspecify @ 2025-06-04 20:25 ` "timtebeek (@timtebeek)" <[email protected]> 2 siblings, 0 replies; 4+ messages in thread From: timtebeek (@timtebeek) @ 2025-06-04 20:25 UTC (permalink / raw) To: pgjdbc/pgjdbc <[email protected]> hi yes we recently added this best practices recipe for JSpecify, both to migrate away from a few existing ones, as well as to add in any potentially missing annotations: https://github.com/openrewrite/rewrite-migrate-java/blob/a130cbbbe4fb70220755a2833100c746e390a5f0/sr... Hope that helps you there! ^ permalink raw reply [nested|flat] 4+ messages in thread
end of thread, other threads:[~2025-06-04 20:25 UTC | newest] Thread overview: 4+ messages (download: mbox mbox.gz follow: Atom feed) -- links below jump to the message on this page -- 2025-05-21 17:50 [pgjdbc/pgjdbc] issue #3634: Migrate nullability annotations from checkerframework to jspecify "vlsi (@vlsi)" <[email protected]> 2025-05-31 09:16 ` "vlsi (@vlsi)" <[email protected]> 2025-06-04 19:05 ` "lobaorn-bitso (@lobaorn-bitso)" <[email protected]> 2025-06-04 20:25 ` "timtebeek (@timtebeek)" <[email protected]>
This inbox is served by agora; see mirroring instructions for how to clone and mirror all data and code used for this inbox