Guillaume Toison

Great, case closed 👍

Also reported here (so an issue in FindSecBugs?) https://github.com/find-sec-bugs/find-sec-bugs/issues/692

Findbugs was renamed Spotbugs but the sonar plugin remained "sonar-findbugs-plugin" for compatibility, so you do have Spotbugs installed, that plugin also comes with its own plugins (find-sec-bugs and fb-contrib).

This message is a simple warning, it wouldn't cause a build error

Not sure if that's what you're looking for (or maybe you found a way already) but the `com.google.errorprone.scanner.BuiltInCheckerSuppliers` class has `ENABLED_WARNINGS` and `ENABLED_ERRORS` sets, you can use them to programmatically...

My comment was for the built-in checkers, I don't think you would need to add your custom checkers in there. From memory the checkers are loaded using the Java service...

Hello, unless I misunderstood this is the same issue as #392 The SonarQube plugin API has deprecated the way we load rules and the new way is apparently due for...

This should be fixed by #2502

This should be fixed by #2502

This should be fixed in version 4.2.3 (just released) Note that the fix needs the SonarQube version to be >= 9.8