Geek Answers Handbook

@SuppressWarnings broken in SonarQube?

In SonarQube 4.5.x LTS, the annotation @SuppressWarningscan be used to suppress false positives in the code, but after upgrading to 5.4 and re-compiling some packages, these previously suppressed problems surfaced. Why?

I was told that the recommendation of SonarSource (the company developing SonarQube) is to suppress false positives from the administrative interface, but we prefer to do this directly in the code for reasons *. The violation below is clearly suppressed by annotation:

The rule violation is still active, although suppressed

Is it @SuppressWarningsno longer processed in SonarQube?

* Reasons include:

  • No dependency on SonarQube database status.
  • No need to rely on SonarQube to identify the old suppressed line of code when changing)

(2017-02-03): SonarQube 6.x

+4
2

3.14 Java- SonarQube, . (4.0). JIRA: SONARJAVA-1719

(3.13.1 ) @SuppressWarnings , .

+4

//NOSONAR . , , SonarCube .

0

More articles:


All Articles