This is an automated email from the ASF dual-hosted git repository.
github-bot pushed a change to branch
dependabot/maven/org.apache.maven.reporting-maven-reporting-impl-4.0.0
in repository https://gitbox.apache.org/repos/asf/maven-dependency-plugin.git
discard 1020ba2a Bump org.apache.maven.reporting:maven-reporting-impl
add 7b137a17 [MDEP-946] Add analyze exclusions to list of goals
add e347ef72 Delete obsolete commented code for issue that was won't fixed
10 years ago (#446)
add b19b7e02 [MDEP-930] Make test robust against platform default
character sets (#448)
add cbac4a78 Bump commons-io:commons-io from 2.16.1 to 2.17.0
add 38ab1007 Bump org.codehaus.plexus:plexus-io from 3.5.0 to 3.5.1
add 361058e3 Bump jettyVersion from 9.4.55.v20240627 to 9.4.56.v20240826
add 188531ca Fix SCM tag
add 7e1aadcd Bump org.apache.commons:commons-lang3 from 3.14.0 to 3.17.0
add 842075d7 Bump org.apache.maven.reporting:maven-reporting-impl
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 (1020ba2a)
\
N -- N -- N
refs/heads/dependabot/maven/org.apache.maven.reporting-maven-reporting-impl-4.0.0
(842075d7)
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 | 10 +++++-----
.../dependency/exclusion/AnalyzeExclusionsMojo.java | 4 ++--
.../AbstractFromConfigurationMojo.java | 16 +++-------------
src/site/apt/index.apt.vm | 2 ++
.../maven/plugins/dependency/tree/TestTreeMojo.java | 19 +++++++------------
5 files changed, 19 insertions(+), 32 deletions(-)
