Guillaume Toison

Thank you very much for looking into it, I did not have much time to investigate but I saw that the code is handling the `@TypeQualifierNickname` on `edu.umd.cs.findbugs.annotation.Nullable` so, indeed,...

Hello @JuditKnoll, How did you see that issue with `edu.umd.cs.findbugs.sarif.Location`? I'm probably doing it the wrong way but I use to build with the `gradlew test` command and then I...

I think that these warnings are from the spotbugs gradle plugin running on spotbugs' own code, so the analysis itself is done from an already released version, not from the...

I have merged the conflict

This is possibly related to #805

Have you tried `org.eclipse.jdt.annotation.NonNullByDefault`? There are references to it, so it seems to be supported

I'm not sure what you want to debate, _sure_ it would be nice if SpotBugs could support more ways to declare nullability, but at the end of the day this...

I don't think we're closing the door to supporting `org.codehaus.commons.nullanalysis.NotNullByDefault`, just trying to say that a reasonable alternative seems to exist already. The project is a bit short on manpower...

This was fixed by https://github.com/find-sec-bugs/find-sec-bugs/pull/680 but unfortunately that is not released yet

The new version of the plugin should be available once SonarSource approves https://github.com/SonarSource/sonar-update-center-properties/pull/510 (they're usually quite fast)