MultipleNullnessAnnotations shouldn't consider Validation Annotations about error-prone HOT 3 OPEN

Yes, thanks. I'm largely clueless about the validation annotations, which I have probably seen as many times in the past couple weeks as I had in my life previously.

We have at least one list of nullness annotations, which sadly includes at least one notably "@NotNull" annotation that is "similar to JSpecify" more than "similar to Jakarta Validation," org.jetbrains.annotations.NotNull. That doesn't make this proposal impossible to implement, but it keeps it from being a one-liner. For now, you might want to set -Xep:MultipleNullnessAnnotations:OFF.

from error-prone.

cc @cpovirk

Thanks for the report. The use-case for MultipleNullnessAnnotations is primarily nullness annotations that have semantics similar to the https://github.com/jspecify/jspecify ones. We could look at having the check skip annotations with incompatible semantics, or clarifying what the use-case for it is.

from error-prone.

Ugh, thanks jetbrains. Fortunately you can probably just use the two official validation spec paths for that. I don't know if I would bother going and tracking down other vendor specific ones. Like I'm sure hibernate had one at some point.

from error-prone.