Bump spotbugs-maven-plugin from 4.5.3.0 to 4.7.3.1

dependabot[bot] commented 1 year ago

Bumps spotbugs-maven-plugin from 4.5.3.0 to 4.7.3.1.

Release notes

Sourced from spotbugs-maven-plugin's releases.

Spotbugs Maven Plugin 4.7.3.1

Still supports spotbugs 4.7.3

Updated to Groovy 4.0.7

Fixes for doxia updates to support maven 4 reporting

Remove invalid usage of 'auxclasspathFromInput' from inception of findbugs maven plugin. This surfaced when running parallel builds and possibly other related issues as it was causing spotbugs to rely on system.in.

Support running xml and sarif reports at same time

Add support to run html reports (htmlOutput parameter). Can be ran along side xml and sarif as well.

Fixed integration tests for maven 3.3.9 confirmed support level.

note: Groovy 4.0.8 / 4.0.9 are broken for this project. Groovy fixed issue which will come with 4.0.10. Therefore, if overriding groovy, do not upgrade currently beyond 4.0.7. Other versions should be otherwise fine.

Spotbugs Maven Plugin 4.7.3.0

Supports spotbugs 4.7.3

note: 4.7.2.2 was released and actually included 4.7.3 by default. All items in 4.7.2.2 are in this release with only change being to denote underlying spotbugs.

Spotbugs Maven Plugin 4.7.2.2

Groovy bumped to 4.0.6

Make sarifOutputDirectory and sarifOutputFilename configurable per #506 and #507

notice: This is actually running spotbugs 4.7.3. A new release will be pushed that directly shows that. Sorry for any confusion.

Spotbugs Maven Plugin 4.7.2.1

Bumps groovy to 4.0.5

Bumps asm to 9.4

Build Related

For reproducible builds, timestamp is now more accurate to the release.

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 information about groovy, security manager, and m2e specific to this application considerations that are often asked about.

... (truncated)

Commits

c399e99 [maven-release-plugin] prepare release spotbugs-maven-plugin-4.7.3.1
89ad8c2 Feature/generate html reports (#161)
78a4e72 Merge pull request #548 from hazendaz/spotbugs
e3c6bb1 [reports] Support running reports for xml and sarif
ce8c130 Merge pull request #547 from spotbugs/renovate/versionspluginversion
5e291b9 Update dependency org.codehaus.mojo:versions-maven-plugin to v2.15.0
0fe498c Merge pull request #546 from hazendaz/spotbugs
17179b7 [ci] Formatting
a446d71 [ci] Cleanup javadocs
8f1f26a Merge pull request #535 from blacelle/RemoveUselessAuxclasspathFromInput
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)