[kotlin:S1144] kotlin.Suppress Annotation does not act the same as java.lang.SuppressWarnings

[TiKevin83 (Travis McGeehan)]

We have a method that has a resilience4j Retry annotation. Resilience4j retry uses a string reference to the name of a method to use as a fallback. This runtime-only reference means that the fallback method is detected as unused at compile time. We can suppress this with an @Suppress annotation from kotlin.Suppress, but it only suppresses the Sonar warning S1144 if we instead use java.lang.SuppressWarnings. This would seem to be an oversight and that the kotlin version @Suppress annotation should work the same as java.lang.SuppressWarnings.

[irina.batinic]

Hi @TiKevin83,

I can’t reproduce your problem, so can you please send me one?
From the code, I see we support kotlin.Suppress and java.lang.SuppressWarnings the same way.

All the best,

Irina

[Colin]

Could you also let us know what versions of what products you’re using (SonarQube, SonarCloud, SonarLint…)

How to Report a False-positive / False-negative

Hey SonarSource Community! False-positives happen, as do false-negatives, and we’re eager to fix them. We are thrilled when our users report problems, so we can make our products better. What is a false-positive (FP)? A false-positive is when an issue is raised unexpectedly on code that should not trigger an issue, or where the suggested action doesn’t make any sense for the code. What is a false-negative (FN)? A false-negative is when an issue should be raised on a piece of code, but isn’t. …