build(deps): bump com.github.spotbugs:spotbugs-maven-plugin from 4.8.6.4 to 4.9.3.2

[dependabot]

Bumps com.github.spotbugs:spotbugs-maven-plugin from 4.8.6.4 to 4.9.3.2.

Release notes

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

Spotbugs Maven Plugin 4.9.3.2

• Fixed long standing bug in source roots of test side of code for exclusion purposes, see #1090 and #1091.

Spotbugs Maven Plugin 4.9.3.1

Plugin

• Rewrite java io to java nio
• Rewrite some groovy code
• Make sure all resources are closed properly
• Don't mix java code into groovy code

Build

• Update github actions
• Add spock for building unit tests and add baseline of tests
• Rewrite all integration tests from java io to java nio
• Add stubfixer to add missing 'Override' annotations to groovy generated code

Spotbugs Maven Plugin 4.9.3.0

Users

• Support spotbugs 4.9.3 release

Build

• Bump junit to 5.12.1
• Bump fluido to 2.1.0

Spotbugs Maven Plugin 4.9.2.0

User Changes

• Supports spotbugs 4.9.2
• Keep jsr 330 compatibility at javax namespace so maven 4 works well since it would cause issues
• Fix ability to use spotbugs plugin with an classifier as it would have previously failed
• Fix possible issue when no output directory supplied and path was used, make it a file
• Move project to use doxia 2 now
• Add some additional debug logging throughout

Build Changes

• Sonar now works
• Fix report plugin name
• Remove coverity and sonar gha actions (sonar was already project level covered)
• Remove coveralls action as it was not used
• Correct sonar issues
• Use more NIO where possible
• Remove all unused items from the base of check/verify mojos as those work against scanned code and play no direct part in the scanning
• Replaced maven artifact transfer with resolver
• Run dependency analyze to fix up build as much as possible
• Stop using 'def' throughout in favor of actual objects
• Move the build to use doxia 2

... (truncated)

Commits

• 887c3c2 [maven-release-plugin] prepare release spotbugs-maven-plugin-4.9.3.2
• caea7a4 Merge pull request #1090 from TeofilisMartisius/master
• 188e19f Set testCompileSourceRoots correctly
• 94d0aa1 Merge pull request #1088 from spotbugs/release/4.9.3.1
• c8e9ca3 [maven-release-plugin] prepare for next development iteration
• 97cfc34 [maven-release-plugin] prepare release spotbugs-maven-plugin-4.9.3.1
• 9479f0f Merge pull request #1085 from hazendaz/nio
• c8a8710 Merge pull request #1086 from spotbugs/renovate/junitversion
• 3095777 Update dependency org.junit.jupiter:junit-jupiter-engine to v5.13.2
• 3e19545 Better path usage dropping internal usage of forward slash as unnecessary
• 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 show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @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)

---

This change is 

[coderabbitai]

Important

Review skipped

Bot user detected.

To trigger a single review, invoke the @coderabbitai review command.

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

---

🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

• Review comments: Directly reply to a review comment made by CodeRabbit. Example:
  • I pushed a fix in commit <commit_id>, please review it.
  • Explain this complex logic.
  • Open a follow-up GitHub issue for this discussion.
• Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
  • @coderabbitai explain this code block.
  • @coderabbitai modularize this function.
• PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
  • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
  • @coderabbitai read src/utils.ts and explain its main purpose.
  • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
  • @coderabbitai help me debug CodeRabbit configuration file.

Support

Need help? Join our Discord community for assistance with any issues or questions.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (Invoked using PR comments)

• @coderabbitai pause to pause the reviews on a PR.
• @coderabbitai resume to resume the paused reviews.
• @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
• @coderabbitai full review to do a full review from scratch and review all the files again.
• @coderabbitai summary to regenerate the summary of the PR.
• @coderabbitai generate sequence diagram to generate a sequence diagram of the changes in this PR.
• @coderabbitai resolve resolve all the CodeRabbit review comments.
• @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
• @coderabbitai help to get help.

Other keywords and placeholders

• Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
• Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
• Add @coderabbitai anywhere in the PR title to generate the title automatically.

CodeRabbit Configuration File (.coderabbit.yaml)

• You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
• Please see the configuration documentation for more information.
• If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Documentation and Community

• Visit our Documentation for detailed information on how to use CodeRabbit.
• Join our Discord Community to get help, request features, and share feedback.
• Follow us on X/Twitter for updates and announcements.