Kengo TODA

memo: it could be nice to support this request by adding a verification type task like: https://docs.gradle.org/current/dsl/org.gradle.testing.jacoco.tasks.JacocoCoverageVerification.html

Just compare the diff of generated reports? Another idea is using [-excludeBugs option](https://spotbugs.readthedocs.io/en/stable/running.html#output-filtering-options) which uses an existing report as "baseline". Then the newly generated report only contain new bugs detected...

refs #90

I guess you upgraded not only spotbugs-gradle-plugin but also Gradle. It could be problem of Gradle side. Make sure you can reproduce this problem with spotbugs-gradle-plugin v3 and the latest...

Then please share the [mcve project](https://stackoverflow.com/help/minimal-reproducible-example) to reproduce. Thanks! But actually what this plugin uses is a Gradle official plugin, so I'm not sure we can provide a fix or...

Yes it's recreated, to eliminate the dependency on Gradle's internal API. [In v3.0.0 we have the SpotBugsReport interface](https://github.com/spotbugs/spotbugs-gradle-plugin/blob/3.0.0/src/main/java/com/github/spotbugs/SpotBugsReports.java) which extends a Gradle internal API. So in v4.0.0 we changed it...

> I'll try to solve this issue, by making a SpotBugsReport interface which extends NamedDomainObjectContainer, and delegate to getByName(String) like v3.0.0. This way doesn't work, because * When we create...

I guess what you need is https://github.com/spotbugs/spotbugs/issues/1385, you may vote or submit a PR to realize it in the SpotBugs core.

Please share [mcve project](https://stackoverflow.com/help/minimal-reproducible-example) to reproduce the issue in our local.

refs https://github.com/gradle/gradle/issues/19073