Bump com.github.spotbugs:spotbugs-maven-plugin from 4.10.3.0 to 4.10.4.0

[dependabot]

Bumps com.github.spotbugs:spotbugs-maven-plugin from 4.10.3.0 to 4.10.4.0.

Release notes

Sourced from com.github.spotbugs:spotbugs-maven-plugin's releases.

spotbugs-maven-plugin-4.10.4.0

What's Changed

• Fixes #1474 by @​gigabitzauber in spotbugs/spotbugs-maven-plugin#1487
• Update build by @​hazendaz in spotbugs/spotbugs-maven-plugin#1494
• Cleanup charset handling and remove never used sourceEncoding in spot… by @​hazendaz in spotbugs/spotbugs-maven-plugin#1495
• Improve javaExecutable usage to prefer current process by @​hazendaz in spotbugs/spotbugs-maven-plugin#1496
• Update deprecated artifact handling by @​hazendaz in spotbugs/spotbugs-maven-plugin#1497
• Require maven 3.8.9 or better by @​hazendaz in spotbugs/spotbugs-maven-plugin#1499
• Add missing javadocs by @​hazendaz in spotbugs/spotbugs-maven-plugin#1500
• Otherwise build updates and library updates

New Contributors

• @​gigabitzauber made their first contribution in spotbugs/spotbugs-maven-plugin#1487

Full Changelog: spotbugs/spotbugs-maven-plugin@spotbugs-maven-plugin-4.10.3.0...spotbugs-maven-plugin-4.10.4.0

Commits

• 698cfa7 [maven-release-plugin] prepare release spotbugs-maven-plugin-4.10.4.0
• f12b09f [pom] Update spotbugs core to 4.10.4
• 2fc78c6 Merge pull request #1500 from hazendaz/master
• 87e41d6 Add more missing javadocs throughout
• b2149c3 [docs] Add missing javadocs to rest of integration tests
• 6cdda40 Merge pull request #1499 from hazendaz/master
• d9d54a6 Merge pull request #1498 from spotbugs/renovate/byte-buddy.version
• 54738d7 Require maven 3.8.9 or better
• d3646ee Update byte-buddy.version to v1.18.12
• 011cbec Merge pull request #1497 from hazendaz/master
• Additional commits viewable in compare view

[bertysentry]

@dependabot rebase

[bertysentry]

The CI failure here is a regression in spotbugs-maven-plugin 4.10.4.0 itself, now tracked upstream in spotbugs/spotbugs-maven-plugin#1511.

TL;DR: 4.10.4.0 (via spotbugs/spotbugs-maven-plugin#1495) stopped normalizing its outputEncoding parameter, whose default is ${project.reporting.outputEncoding} — a property this POM didn't define. The Groovy-generated getter overrides AbstractMavenReport.getOutputEncoding()'s null-safe fallback, so the site report goal crashes with NullPointerException: charsetName in reportToSite when writing the report page. It only reproduces on a clean build (a warm target/site skips the writing path), which is why it looked CI-only. The compat-test failures in the log are the usual ignored failsafe results, unrelated.

Pushed 1388986 defining <project.reporting.outputEncoding>UTF-8</project.reporting.outputEncoding>, verified locally with a clean mvn verify site on JDK 17 (fails without it, green with it).