dependabot[bot] opened a new pull request, #889: URL: https://github.com/apache/logging-log4j2/pull/889
Bumps [spotbugs-maven-plugin](https://github.com/spotbugs/spotbugs-maven-plugin) from 4.0.4 to 4.7.0.0. <details> <summary>Release notes</summary> <p><em>Sourced from <a href="https://github.com/spotbugs/spotbugs-maven-plugin/releases";>spotbugs-maven-plugin's releases</a>.</em></p> <blockquote> <h2>Spotbugs-maven-plugin 4.7.0.0</h2> <ul> <li>Support spotbugs 4.7.0</li> <li>Fix <a href="https://github-redirect.dependabot.com/spotbugs/spotbugs-maven-plugin/issues/68";>#68</a>, note still requires use of a separate plugin, see [here}(https://github.com/spotbugs/spotbugs-maven-plugin#eclipse-m2e-integration)</li> <li>Fix <a href="https://github-redirect.dependabot.com/spotbugs/spotbugs-maven-plugin/issues/114";>#114</a> 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.</li> <li>Updated readme with various informatino about groovy, security manager, and m2e specific to this application considerations that are often asked about.</li> </ul> <h2>Spotbugs-maven-plugin 4.6.0.0</h2> <ul> <li>Spotbugs 4.6.0 support</li> <li>Groovy 4.0.1 based</li> </ul> <p>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.</p> <p>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.</p> <h2>Spotbugs-maven-plugin 4.5.3.0</h2> <ul> <li>Support spotbugs maven plugin 4.5.3.0</li> <li>Make maven scoped dependencies provided scope</li> </ul> <h2>Spotbugs-maven-plugin 4.5.2.0</h2> <ul> <li>Support spotbugs 4.5.2</li> <li>Fix deprecations from spotbugs 4.5.0</li> </ul> <h2>Spotbugs-maven-plugin 4.5.0.0</h2> <p>support for spotbugs 4.5.0</p> <h2>Spotbugs-maven-plugin 4.4.2.2</h2> <ul> <li>Use new base-parent pom with removal of undocumented maven url attributes that cause issues for users of older jfrog artifactory installations.</li> </ul> <h2>Spotbugs-maven-plugin 4.4.2.1 Release</h2> <ul> <li>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.</li> <li>This patch release addresses issues with resolution of the maven dependencies that resulted in a few regression libraries that had vulnerabilities.</li> <li>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.</li> </ul> <h2>Spotbugs-maven-plugin 4.4.2 Release</h2> <p>Added support for spotbugs 4.4.2 Now running github actions on jdk 17 and 18-ea to show this works there Now running against maven 3.8.3 Updated a number of plugins and dependencies</p> <h2>Spotbugs-maven-plugin 4.4.1 Release</h2> <ul> <li>Add support for Sarif</li> <li>Support spotbugs 4.4.1</li> <li>Library Updates</li> </ul> <h2>Spotbugs-maven-plugin 4.3.0</h2> <ul> <li>Support of spotbugs 4.3.0</li> <li>Add support for systemPropertyVariables</li> <li>Support jdk 17</li> </ul> <h2>Spotbugs Maven Plugin 4.2.3</h2> <!-- raw HTML omitted --> </blockquote> <p>... (truncated)</p> </details> <details> <summary>Commits</summary> <ul> <li><a href="https://github.com/spotbugs/spotbugs-maven-plugin/commit/f08f5990d4173d7b0e64939b0f3d7c9da5da39ca";><code>f08f599</code></a> [maven-release-plugin] prepare release spotbugs-maven-plugin-4.7.0.0</li> <li><a href="https://github.com/spotbugs/spotbugs-maven-plugin/commit/a45eac35b7f2cdb017aec29f107f3637fd023352";><code>a45eac3</code></a> [pom] Skip pdf plugin as it doesn't work well</li> <li><a href="https://github.com/spotbugs/spotbugs-maven-plugin/commit/8e86861cfc3b7f018163e5a542d2e0a3ea6b63ff";><code>8e86861</code></a> Merge pull request <a href="https://github-redirect.dependabot.com/spotbugs/spotbugs-maven-plugin/issues/434";>#434</a> from hazendaz/spotbugs</li> <li><a href="https://github.com/spotbugs/spotbugs-maven-plugin/commit/bc6bad23c1c078a229510e9e87474e65709725fa";><code>bc6bad2</code></a> Merge pull request <a href="https://github-redirect.dependabot.com/spotbugs/spotbugs-maven-plugin/issues/433";>#433</a> from spotbugs/dependabot/maven/org.codehaus.plexus-pl...</li> <li><a href="https://github.com/spotbugs/spotbugs-maven-plugin/commit/02a5e756ce695aec8849a9ecc2c5894a47f8a2eb";><code>02a5e75</code></a> [pom] Bump jxr plugin to 3.2.0</li> <li><a href="https://github.com/spotbugs/spotbugs-maven-plugin/commit/0036acfefcc3729b83874631db84949a2025de7d";><code>0036acf</code></a> [pom] Bump findsecbugs IT to 1.12.0</li> <li><a href="https://github.com/spotbugs/spotbugs-maven-plugin/commit/623220ea4a62b58e965c7b6159929e1bd9b74233";><code>623220e</code></a> [pom] Bump IT compiler to 3.10.1</li> <li><a href="https://github.com/spotbugs/spotbugs-maven-plugin/commit/c21d15a63ab5ada3798c17cff808a6453320d36b";><code>c21d15a</code></a> [actions] Use jdk 11 with site for now</li> <li><a href="https://github.com/spotbugs/spotbugs-maven-plugin/commit/c5bff4703bc7146948b52bb2c209dd8442293530";><code>c5bff47</code></a> [pom] Update comment in pom</li> <li><a href="https://github.com/spotbugs/spotbugs-maven-plugin/commit/e9bf09ce01072c610b43325f068527bc0f717cad";><code>e9bf09c</code></a> Bump plexus-utils from 3.4.1 to 3.4.2</li> <li>Additional commits viewable in <a href="https://github.com/spotbugs/spotbugs-maven-plugin/compare/spotbugs-maven-plugin-4.0.4...spotbugs-maven-plugin-4.7.0.0";>compare view</a></li> </ul> </details> <br /> [](https://docs.github.com/en/github/managing-security-vulnerabilities/about-dependabot-security-updates#about-compatibility-scores) 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-automerge-start) [//]: # (dependabot-automerge-end) --- <details> <summary>Dependabot commands and options</summary> <br /> 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) </details> -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
