dependabot[bot] opened a new pull request, #751:
URL: https://github.com/apache/directory-scimple/pull/751

   Bumps 
[com.github.spotbugs:spotbugs-maven-plugin](https://github.com/spotbugs/spotbugs-maven-plugin)
 from 4.8.6.6 to 4.9.1.0.
   <details>
   <summary>Release notes</summary>
   <p><em>Sourced from <a 
href="https://github.com/spotbugs/spotbugs-maven-plugin/releases";>com.github.spotbugs:spotbugs-maven-plugin's
 releases</a>.</em></p>
   <blockquote>
   <h2>Spotbugs Maven Plugin 4.9.1.0</h2>
   <ul>
   <li>Supports spotbugs 4.9.1</li>
   </ul>
   <p>build</p>
   <ul>
   <li>Move plugin configuration from reporting section to plugin 
management</li>
   </ul>
   <h2>Spotbugs Maven Plugin 4.9.0.0</h2>
   <h2>Project</h2>
   <ul>
   <li>Requires java 11 now</li>
   <li>Support spotbugs 4.9.0</li>
   <li>Update plugins / dependencies</li>
   <li>cleanup some output logging that occurs during usage</li>
   <li>Use more concrete object definitions instead of 'def'</li>
   <li>Use Path.of instead of Paths.get</li>
   <li>Update javadoc that default character encoding is utf-8 not the system 
default.  This has not been true in a very long time.</li>
   </ul>
   <h2>Build 33</h2>
   <ul>
   <li>Add information on how to override with newer spotbugs as its rare that 
the maven plugin has any specific changes related to the spotbugs core 
updates.</li>
   <li>github action updates</li>
   <li>restructure entire pom to make use of dependency management to make it 
more clear we ware overriding libraries rather than using then and check 
dependency analyzer to see its decreasing invalid setup.  This is intended to 
help when moving to doxia 2 which is still in progress.</li>
   <li>Use more dependency management setup</li>
   <li>reduce spotbugs variables so that renovate updates in fact update 
fully</li>
   <li>override any plugins from parent that now require doxia 2 back to their 
doxia 1 counterparts</li>
   <li>avoid transfer progress output throughout</li>
   <li>cleanup many warnings inside integration tests</li>
   </ul>
   <p>note: Before this release, we had been forked off the original 
findbugs-maven-plugin.  As that plugin points back here and give so many 
commits ahead, github was used to break the fork and retain all information 
otherwise which also updated all forks.</p>
   </blockquote>
   </details>
   <details>
   <summary>Commits</summary>
   <ul>
   <li><a 
href="https://github.com/spotbugs/spotbugs-maven-plugin/commit/a94d8316378cd0ab8461f82de2d888b689db902b";><code>a94d831</code></a>
 [maven-release-plugin] prepare release spotbugs-maven-plugin-4.9.1.0</li>
   <li><a 
href="https://github.com/spotbugs/spotbugs-maven-plugin/commit/fa361ca9493a34e4ce8ae354fdc51e4f256db2b4";><code>fa361ca</code></a>
 [pom] Formatting</li>
   <li><a 
href="https://github.com/spotbugs/spotbugs-maven-plugin/commit/5f9e363718b79fca9a0609159d36cd4fa6b6a42c";><code>5f9e363</code></a>
 [pom] Bump project to spotbugs 4.9.1.0-SNAPSHOT</li>
   <li><a 
href="https://github.com/spotbugs/spotbugs-maven-plugin/commit/557df818f80d3356371df69ce627a50795809064";><code>557df81</code></a>
 Merge pull request <a 
href="https://redirect.github.com/spotbugs/spotbugs-maven-plugin/issues/986";>#986</a>
 from spotbugs/renovate/spotbugs.version</li>
   <li><a 
href="https://github.com/spotbugs/spotbugs-maven-plugin/commit/334187e1f6aae3b90190d8b3c52406e531581f19";><code>334187e</code></a>
 Update spotbugs.version to v4.9.1</li>
   <li><a 
href="https://github.com/spotbugs/spotbugs-maven-plugin/commit/0711f0b634a1bc8c93609c5f479f76c732990b8f";><code>0711f0b</code></a>
 Merge pull request <a 
href="https://redirect.github.com/spotbugs/spotbugs-maven-plugin/issues/997";>#997</a>
 from spotbugs/release/4.9.0</li>
   <li><a 
href="https://github.com/spotbugs/spotbugs-maven-plugin/commit/60cfbe0cccb05bee615f28777571fb01f7cc1213";><code>60cfbe0</code></a>
 [pom] Move reporting configuration to plugin management</li>
   <li><a 
href="https://github.com/spotbugs/spotbugs-maven-plugin/commit/95a8eea8c0ca94410575ee4cc29bf9377b059062";><code>95a8eea</code></a>
 [maven-release-plugin] prepare for next development iteration</li>
   <li><a 
href="https://github.com/spotbugs/spotbugs-maven-plugin/commit/bda340ab6d7db7c4f132e9ac0cecca16aae92d06";><code>bda340a</code></a>
 [maven-release-plugin] prepare release spotbugs-maven-plugin-4.9.0.0</li>
   <li><a 
href="https://github.com/spotbugs/spotbugs-maven-plugin/commit/c1dd4d91b7287b2219e5df67f9148d8406b5c814";><code>c1dd4d9</code></a>
 Merge pull request <a 
href="https://redirect.github.com/spotbugs/spotbugs-maven-plugin/issues/995";>#995</a>
 from spotbugs/renovate/beanutils.version</li>
   <li>Additional commits viewable in <a 
href="https://github.com/spotbugs/spotbugs-maven-plugin/compare/spotbugs-maven-plugin-4.8.6.6...spotbugs-maven-plugin-4.9.1.0";>compare
 view</a></li>
   </ul>
   </details>
   <br />
   
   
   [![Dependabot compatibility 
score](https://dependabot-badges.githubapp.com/badges/compatibility_score?dependency-name=com.github.spotbugs:spotbugs-maven-plugin&package-manager=maven&previous-version=4.8.6.6&new-version=4.9.1.0)](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 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)
   
   
   </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: dev-unsubscr...@directory.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@directory.apache.org
For additional commands, e-mail: dev-h...@directory.apache.org

Reply via email to