Skip to content

Releases: spotbugs/spotbugs-maven-plugin

Spotbugs Maven Plugin 4.7.3.0

07 Nov 18:48
Compare
Choose a tag to compare
  • 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

06 Nov 16:55
Compare
Choose a tag to compare
  • 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

08 Oct 03:28
Compare
Choose a tag to compare
  • 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

06 Sep 02:08
Compare
Choose a tag to compare
  • support for spotbugs 4.7.2

Spotbugs Maven Plugin 4.7.1.1

24 Jul 17:24
Compare
Choose a tag to compare

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

06 Jul 20:56
Compare
Choose a tag to compare
  • 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

20 May 03:11
Compare
Choose a tag to compare
  • 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.

Spotbugs-maven-plugin 4.6.0.0

24 Mar 19:47
Compare
Choose a tag to compare
  • 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

05 Jan 17:07
Compare
Choose a tag to compare
  • Support spotbugs maven plugin 4.5.3.0
  • Make maven scoped dependencies provided scope

Spotbugs-maven-plugin 4.5.2.0

21 Dec 23:37
Compare
Choose a tag to compare
  • Support spotbugs 4.5.2
  • Fix deprecations from spotbugs 4.5.0