We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
com.google.code.findbugs:jsr305
Since we use guava version 32.x.x.
guava
Like here: playframework/playframework@d6cccba
The text was updated successfully, but these errors were encountered:
Guava migrated to https://mvnrepository.com/artifact/org.checkerframework/checker-qual/3.35.0 (210k where jsr305 was 12k).
Internally we use org.jetbrains:annotations (29k).
org.jetbrains:annotations
All annotations that the Kotlin compiler understands are listed here:
https://github.com/JetBrains/kotlin/blob/master/core/compiler.common.jvm/src/org/jetbrains/kotlin/load/java/JvmAnnotationNames.kt
I can make a PR replacing the use of jsr305 with whatever is chosen.
Sorry, something went wrong.
@cies Yes, why not. We can upgrade to whatever newer library. I don't see any reasons to prefer one of them over others.
But I personally like annotations with javax. prefix (like javax.annotation.Nullable) - just because they look like a standard. :)
javax.
javax.annotation.Nullable
I was mistaken. Guava has not migrated yet. The discussion here:
google/guava#2960
That thread is linked to by several other projects, and they usually migrate to jetbrains-annontations or checker-qual.
I'd opt for snoozing this until Guava makes the switch and then follow their choice (not to add any more dependencies).
Guava is still not decided. Lol.
cies
No branches or pull requests
Since we use
guava
version 32.x.x.Like here: playframework/playframework@d6cccba
The text was updated successfully, but these errors were encountered: