@SuppressWarnings behaviour changed since SonarQube 8.X

The java analyzer plugin provided in SonarQube before 8.X, was filtering issues of all other plugin targeting the java language. It was not intentional, from the java analyzer plugin point of view, but users were able to filter rules like:

@SuppressWarnings({"java:S1166", "javasecurity:S5131", "findsecbugs:PATH_TRAVERSAL_IN"})

Since SonarQube 8.X, the java analyzer plugin only filters its own issues and issues from its custom rules and not any more issues from other plugins like javasecurity or findsecbugs.

Note
This topic is related to @SuppressWarnings are not honored by the SonarQube 7.9 anymore
But the impact on SonarQube 7.9 LTS was considered as regression and the topic has been resolved by a bug fix release 6.3.2 of the java analyzer.
By contrast, this topic is about SonarQube 8.X and the problem is not resolved.

Hi,

Thank you for the information, I faced with the same problem with SonarQube 8.3.1. Can we expect a solution in the near future for SonarQube 8.x? Will there be a ticket what can be tracked?

Is it possible to workaround this somehow?

Thanks in advance!

1 Like