-
Notifications
You must be signed in to change notification settings - Fork 133
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
Replace Jetbrains with Jakarta annotations #482
Conversation
NB: it's already done on Quarkus pr |
Correct. That's where it's from - to reduce the amount of changes from that PR |
Love it 😀 |
`org.jetbrains.annotations.NotNull`/`Nullable` -> `jakarta.annotations.Nonnull`/`Nullable` plus Guava's `VisibleForTesting` The Jakarta annotations are likely better supported by validation frameworks like Hibernate Validator.
424062b
to
e9c0c38
Compare
LGTM; but can we add this to the linter? I would hate to see us accidentally regress back to the wrong ones. |
@@ -45,7 +45,7 @@ dependencies { | |||
} | |||
} | |||
|
|||
compileOnly(libs.jetbrains.annotations) | |||
compileOnly(libs.jakarta.annotation.api) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Or will the build changes make it impossible to accidentally use the wrong annotation?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yes, this
org.jetbrains.annotations.NotNull
/Nullable
->jakarta.annotations.Nonnull
/Nullable
plus Guava'sVisibleForTesting
The Jakarta annotations are likely better supported by validation frameworks like Hibernate Validator.