Bump spotbugs-maven-plugin from 4.2.3 to 4.7.2.0

[dependabot]

Bumps spotbugs-maven-plugin from 4.2.3 to 4.7.2.0.

Release notes

Sourced from spotbugs-maven-plugin's releases.

Spotbugs Maven Plugin 4.7.2.0

• support for spotbugs 4.7.2

Spotbugs Maven Plugin 4.7.1.1

Patch Release

• Validate Spotbugs report even if only test sources exist fixing #454
• Moved javaparser-core to project level to resolve issues with site releases
• Code cleanup throughout
• General build updates
• Fixed l10n on site documentation

Spotbugs Maven Plugin 4.7.1.0

• Support spotbugs 4.7.1
• Add support for multiple bug inclusion, excusion, and baseline files. See PR #436
• Build Updates including usage of asm bom, groovy bom, and adjustment to asm to ensure it works after maven changes
• Invoker plugin set to groovy 3 while project is groovy 4 as invoker needs older groovy.

Spotbugs-maven-plugin 4.7.0.0

• Support spotbugs 4.7.0
• Fix #68, note still requires use of a separate plugin, see [here}(https://github.com/spotbugs/spotbugs-maven-plugin#eclipse-m2e-integration)
• Fix #114 by introducing verify mojo to allow split of analysis and verification into lifecycle phases of one's choosing. One use case for that is running multiple code analyzers at once and only failing the build at a later stage, so that all of them have a chance to run. Verify then in this case just uses an existing file.
• Updated readme with various informatino about groovy, security manager, and m2e specific to this application considerations that are often asked about.

Spotbugs-maven-plugin 4.6.0.0

• Spotbugs 4.6.0 support
• Groovy 4.0.1 based

note on groovy: If using groovy with same group id (already existing condition), an error may occur if not on same version. To alleviate that, make sure groovy artifacts are defined in dependency management in order to force the loaded version correctly on your usage.

note on 4.6.0.1/4.6.0.2: no change, not released. Issue with site distribution via maven release plugin only that is being tested, use 4.6.0.0 only.

Spotbugs-maven-plugin 4.5.3.0

• Support spotbugs maven plugin 4.5.3.0
• Make maven scoped dependencies provided scope

Spotbugs-maven-plugin 4.5.2.0

• Support spotbugs 4.5.2
• Fix deprecations from spotbugs 4.5.0

Spotbugs-maven-plugin 4.5.0.0

support for spotbugs 4.5.0

Spotbugs-maven-plugin 4.4.2.2

• Use new base-parent pom with removal of undocumented maven url attributes that cause issues for users of older jfrog artifactory installations.

Spotbugs-maven-plugin 4.4.2.1 Release

• Reworked version string to account for any patches we need to make to plugin that would otherwise case a diverge from spotbugs or require us to wait. This is similar to how other plugins approach this such as lombok. The first 3 positions are reserved for the alignment with spotbugs. The last position is for our patch revision level. Normally this would be '0' but given we released 4.4.2 already, it made sense to denote '1' so that it was clear there was a difference.
• This patch release addresses issues with resolution of the maven dependencies that resulted in a few regression libraries that had vulnerabilities.
• This patch further changed lowest maven from 3.2.5 to 3.3.9 but reality is that even 3.3.9 likely doesn't work. Since all maven before 3.8.1 are vulnerable, most should be there. If not, let us know. Future releases will raise that revision number up.

... (truncated)

Commits

• 094bf44 [maven-release-plugin] prepare release spotbugs-maven-plugin-4.7.2.0
• a124305 Merge pull request #485 from hazendaz/spotbugs
• 97012fa [pom] Bump junit to 5.9.0
• ea6cb7c [pom] Bump remainder of spotbugs to 4.7.2
• 0e2d503 Merge pull request #483 from spotbugs/renovate/major-slf4jversion
• 3faea35 Merge branch 'spotbugs' into renovate/major-slf4jversion
• 7c40f37 Merge pull request #484 from spotbugs/renovate/spotbugsversion
• 01758a3 Update dependency com.github.spotbugs:spotbugs to v4.7.2
• dfeae38 Update slf4jVersion to v2
• d39ff02 Merge pull request #481 from spotbugs/renovate/javadocpluginversion
• Additional commits viewable in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot merge will merge this PR after your CI passes on it
• @dependabot squash and merge will squash and merge this PR after your CI passes on it
• @dependabot cancel merge will cancel a previously requested merge and block automerging
• @dependabot reopen will reopen this PR if it is closed
• @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

[dependabot]

Superseded by #47.