[logging-log4j2] branch dependabot/maven/com.github.spotbugs-spotbugs-maven-plugin-4.7.2.0 updated (dc8a905c3d -> 5dcf2fd78e)

[gi...@apache.org]

This is an automated email from the ASF dual-hosted git repository.

github-bot pushed a change to branch dependabot/maven/com.github.spotbugs-spotbugs-maven-plugin-4.7.2.0
in repository https://gitbox.apache.org/repos/asf/logging-log4j2.git


 discard dc8a905c3d Bump spotbugs-maven-plugin from 4.7.0.0 to 4.7.2.0
     add 63d11af1b8 Bump maven-toolchains-plugin from 3.0.0 to 3.1.0
     add ceeed0e09a Add missing `maven-scm-plugin` version
     add 6ba5c59b2d Bump maven-jxr-plugin from 3.2.0 to 3.3.0
     add f4b9a475e4 Bump maven-checkstyle-plugin from 3.1.2 to 3.2.0
     add 03d26ff2fa Bump checkstyle from 8.45.1 to 9.3
     add 82628b8bb3 Bump maven-pmd-plugin from 3.16.0 to 3.19.0
     add 5dcf2fd78e Bump spotbugs-maven-plugin from 4.7.0.0 to 4.7.2.0

This update added new revisions after undoing existing revisions.
That is to say, some revisions that were in the old version of the
branch are not in the new version.  This situation occurs
when a user --force pushes a change and generates a repository
containing something like this:

 * -- * -- B -- O -- O -- O   (dc8a905c3d)
            \
             N -- N -- N   refs/heads/dependabot/maven/com.github.spotbugs-spotbugs-maven-plugin-4.7.2.0 (5dcf2fd78e)

You should already have received notification emails for all of the O
revisions, and so the following emails describe only the N revisions
from the common base, B.

Any revisions marked "omit" are not gone; other references still
refer to them.  Any revisions marked "discard" are gone forever.

No new revisions were added by this update.

Summary of changes:
 pom.xml | 11 ++++++-----
 1 file changed, 6 insertions(+), 5 deletions(-)