chore(deps): bump com.github.spotbugs:spotbugs-maven-plugin from 4.7.3.4 to 4.8.6.1 in /jans-orm

[dependabot]

Bumps com.github.spotbugs:spotbugs-maven-plugin from 4.7.3.4 to 4.8.6.1.

Release notes

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

Spotbugs Maven Plugin 4.8.6.1

• Supports spotbugs 4.8.6
• Restore java 8 support

Spotbugs Maven Plugin 4.8.6.0

Support spotbugs 4.8.6

WARNING: This version accidentally required java 11. A patch is incoming that will move back to java 8. Do note though spotbugs will be moving up in near future.

Spotbugs Maven Plugin 4.8.5.0

• Support spotbugs 4.8.5.0
• Dependency and plugin general updates
• Maven wrapper update to 3.3.1

Spotbugs Maven Plugin 4.8.4.0

User

• Support spotbugs 4.8.4
• library updates / plugin updates
• Supports jdk 23
• Require maven 3.6.3 per maven deprecation

Build

• Update renovate config
• Update GHA for adjustments to maven/java
• Drop modernizer plugin back to 2.7.0 as it was restricted to maven 3.9.5 (will be fixed on next release)

Spotbugs Maven Plugin 4.8.3.1

• Support for spotbugs 4.8.3
• Bump groovy to 4.0.18
• Bump slf4j to 2.0.12
• Bump commons codec to 1.16.1

Spotbugs Maven Plugin 4.8.3.0

This release is much larger than most, all IT tests are good to go. Given scope of changes, if any issues seen, please raise ticket so we can quickly address. A lot was done here to fix-up lazy groovy usage.

Consumer

• Support for spotbugs 4.8.3
• library updates
• Add 'noClassOk' option (untested)
• Stop overusing 'def' from groovy and use concrete types
• Many plexus to standard java usage
• Switch 'Boolean' to 'boolean' for parameters
• Remove long deprecated and not actually used spotbugsXmlOutput
• Switch to using buffered writer
• Drop supporting 2005 version of jxr-maven-plugin
• Add support for usage of classifier (untested)
• Add better logging when plugin skipped

... (truncated)

Commits

• 5adc7fb [maven-release-plugin] prepare release spotbugs-maven-plugin-4.8.6.1
• 8027008 Merge pull request #836 from hazendaz/master
• 59b4219 Merge pull request #835 from spotbugs/renovate/inforeportspluginversion
• 138fdb5 [pom] Drop runtime back to java 8 requirement until spotbugs goes to 11 or be...
• 9594a0a Update dependency org.apache.maven.plugins:maven-project-info-reports-plugin ...
• 850f0cf Merge pull request #833 from spotbugs/release/4.8.6.0
• 1633dfc [maven-release-plugin] prepare for next development iteration
• be70f9e [maven-release-plugin] prepare release spotbugs-maven-plugin-4.8.6.0
• 9614424 [pom] Bump remainder of spotbugs items to 4.8.6
• d3b7c91 Merge pull request #829 from spotbugs/renovate/spotbugsversion
• Additional commits viewable in compare view

You can trigger a rebase of this PR 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)

\nPlease check the below before submitting your PR. The PR will not be merged if there are no commits that start with `docs:` to indicate documentation changes or if the below checklist is not selected.\n- [x] **I confirm that there is no impact on the docs due to the code changes in this PR.**

Note
Automatic rebases have been disabled on this pull request as it has been open for over 30 days.

[dryrunsecurity]

Hi there 👋, @DryRunSecurity here, below is a summary of our analysis and findings.

DryRun Security	Status	Findings
Server-Side Request Forgery Analyzer	✅	0 findings
Configured Codepaths Analyzer	✅	0 findings
Secrets Analyzer	✅	0 findings
Authn/Authz Analyzer	✅	0 findings
SQL Injection Analyzer	✅	0 findings
Sensitive Files Analyzer	❕	1 finding
IDOR Analyzer	✅	0 findings

Note

🟢 Risk threshold not exceeded.

Change Summary (click to expand)

The following is a summary of changes in this pull request made by me, your security buddy 🤖. Note that this summary is auto-generated and not meant to be a definitive list of security issues but rather a helpful summary from a security perspective.

Summary:

The code change in this pull request updates the version of the spotbugs-maven-plugin from 4.7.3.4 to 4.8.6.2. SpotBugs is a static code analysis tool that helps identify potential bugs in Java applications. This change is positive from an application security perspective, as it updates the plugin to a newer version, which may include bug fixes, security improvements, and enhanced detection capabilities. Keeping dependencies up-to-date is an important security practice, as it helps address known vulnerabilities and improve the overall security posture of the application. The rest of the changes in the pom.xml file appear to be updates to the project's build configuration, which, while not directly impacting the application's security, are important for ensuring the overall quality and security of the application.

Files Changed:

• jans-orm/pom.xml: This file contains the project's build configuration, including various Maven plugins and their versions. The key change in this pull request is the update of the spotbugs-maven-plugin version from 4.7.3.4 to 4.8.6.2. This change is a positive security enhancement, as it helps keep the static code analysis tool up-to-date and potentially improves the identification of potential bugs and vulnerabilities in the application.

Powered by DryRun Security

[dryrunsecurity]

DryRun Security Summary

The provided code change updates the spotbugs-maven-plugin version in the jans-orm/pom.xml file from 4.7.3.4 to 4.8.6.2, which is generally positive from a security perspective as it allows the project to benefit from the latest bug fixes and improvements in the SpotBugs tool.

Expand for full summary

Summary:

The provided code change is an update to the version of the spotbugs-maven-plugin used in the jans-orm/pom.xml file. The previous version 4.7.3.4 has been updated to 4.8.6.2. From an application security perspective, this change is generally positive, as it indicates the project maintainers are keeping their dependencies up-to-date. Updating to the latest version of the SpotBugs Maven Plugin can help identify and address potential security vulnerabilities in the codebase. SpotBugs is a static code analysis tool that can detect a wide range of potential issues, including security-related bugs. By using the latest version of the plugin, the project can benefit from the latest bug fixes and improvements in the underlying SpotBugs tool. Overall, this code change appears to be a routine dependency update that should help improve the security and quality of the jans-orm project.

Files Changed:

• jans-orm/pom.xml: This file has been updated to use the latest version of the spotbugs-maven-plugin, which has been upgraded from 4.7.3.4 to 4.8.6.2. This change is generally positive from a security perspective, as it allows the project to benefit from the latest bug fixes and improvements in the SpotBugs tool, which can help identify and address potential security vulnerabilities in the codebase.

Code Analysis

We ran 7 analyzers against 1 file and 1 analyzer had findings. 6 analyzers had no findings.

Analyzer	Findings
Sensitive Files Analyzer	1 finding

Riskiness

🟢 Risk threshold not exceeded.

View PR in the DryRun Dashboard.

[dependabot]

Superseded by #9380.