-
Notifications
You must be signed in to change notification settings - Fork 54
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[not for review yet] deps: changing jsr305 to jspecify #3191
base: main
Are you sure you want to change the base?
Conversation
Preparation for b/341380807 Following https://jspecify.dev/docs/using/#if-your-code-already-uses-jsr-305-annotations
The build failed:
|
ci / build(8) for gapic-generator-java failed: https://github.com/googleapis/sdk-platform-java/actions/runs/10837827237/job/30074668962?pr=3191
I need to add jspecify dependency in the Bazel build too. |
"ci / build(8) except for gapic-generator-java" passed. |
There are differnces in the AutoValue generated code. https://gist.github.com/suztomo/0dc82b1b04d9364ecb35421f8b65cc63 Update: They are irrelevant. AutoValue is adding the Nullable for the builder fields that can be null at initialization when type annotation is found. |
Quality Gate passed for 'gapic-generator-java-root'Issues Measures |
Quality Gate passed for 'java_showcase_integration_tests'Issues Measures |
Preparation for b/341380807. Following https://jspecify.dev/docs/using/#if-your-code-already-uses-jsr-305-annotations
com.google.code.findbugs:jsr305
toorg.jspecify:1.0.0
in pom.xmlimport javax.annotation.Nullable;
toimport org.jspecify.annotations.Nullable;
import javax.annotation.Nonnull;
toimport org.jspecify.annotations.NonNull;
and change@Nonnull
toNonNull
.