This is an automated email from the ASF dual-hosted git repository.
github-bot pushed a change to branch dependabot/maven/slf4jVersion-2.0.0
in repository https://gitbox.apache.org/repos/asf/maven-pmd-plugin.git
discard fc4361d Bump slf4jVersion from 1.7.36 to 2.0.0
add b55fb9a (doc) Update releasenotes.md
add 584ac6d Bump release-drafter/release-drafter from 5.20.0 to 5.20.1
(#86)
add 1d7a2fb Set next dev version to 3.19.0-SNAPSHOT
add 7b4c330 [MPMD-353] - API incompatibility with jansi after upgrading
m-shared-utils (#91)
add ebd3579 [MPMD-354] - Upgrade to PMD 6.49.0 (#92)
add 6925e0a Bump slf4jVersion from 1.7.36 to 2.0.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 (fc4361d)
\
N -- N -- N refs/heads/dependabot/maven/slf4jVersion-2.0.0
(6925e0a)
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:
.github/workflows/release-drafter.yml | 2 +-
pom.xml | 4 +--
.../org/apache/maven/plugins/pmd/CpdReport.java | 2 --
.../org/apache/maven/plugins/pmd/PmdReport.java | 2 --
.../apache/maven/plugins/pmd/exec/CpdExecutor.java | 2 +-
.../apache/maven/plugins/pmd/exec/CpdRequest.java | 11 --------
.../apache/maven/plugins/pmd/exec/Executor.java | 5 +---
.../apache/maven/plugins/pmd/exec/PmdExecutor.java | 2 +-
.../apache/maven/plugins/pmd/exec/PmdRequest.java | 11 --------
.../apt/examples/upgrading-PMD-at-runtime.apt.vm | 2 ++
src/site/markdown/releasenotes.md | 32 +++++++++++++++++++---
11 files changed, 36 insertions(+), 39 deletions(-)
