Guillaume Toison

The SonarQube version shouldn't matter too much, but I guess you also updated the sonar-findbugs plugin at the same time? Basically the analysis is running in your build, and then...

Ok, so that version of the plugin was using SpotBugs 4.4.0 (release in 2021) while the newer version you're using is SpotBugs 4.8.2 Do you think you can share a...

Thank you for the log file but what I need to look into this is the compiled .class file triggering the problem. The sources are compiled into .class files and...

Thanks, is this the same issue as the separately reported https://github.com/spotbugs/spotbugs/issues/2861? Would it be possible to have some kind of anonymized version of the code for the problematic methods? The...

Some of the issues we've seen recently: - Different compilers produce different bytecode so it might be relevant to know the exact compiler (and version) you're using - Some build...

This is the same issue as https://github.com/spotbugs/spotbugs/issues/1992 most probably

My understanding (based on https://github.com/spotbugs/spotbugs/pull/1435#issuecomment-783161822 and https://github.com/spotbugs/spotbugs/issues/1992) is that the issue was actually caused by compilers (ecj, javac) producing some redudant bytecode. Maybe while testing with the gradle plugin you...

I think you need to share a way of reproducing the problem or we won't be able to help. My understanding is that the issue is with the compiler, because...

FindBugs is the original name of the project. SonarSource made a plugin to use it in SonarQube. When FindBugs was renamed SpotBugs the plugin kept using the FindBugs name, because...

I think that you are referring to the JDK running your SonarQube server, but that shouldn't matter here.