This is an automated email from the ASF dual-hosted git repository.
github-bot pushed a change to branch
dependabot/maven/org.assertj-assertj-core-3.27.6
in repository https://gitbox.apache.org/repos/asf/maven-javadoc-plugin.git
discard 83da5b7f Bump org.assertj:assertj-core from 3.27.4 to 3.27.6
add 20c6e04b Bump org.codehaus.plexus:plexus-io from 3.5.1 to 3.5.2
add 51e3c59b Update JDK matrix to include version 25
add b9133386 Bump org.apache.commons:commons-lang3 from 3.18.0 to 3.19.0
add b453602a Fix MalformedInputException on Windows with Java 8 due to
charset mis… (#1274)
add 8cb7c5cb Use consistently the encoding expected by Javadoc for reading
and writing of data (#1278)
add 3d1d6b8e Bump org.assertj:assertj-core from 3.27.4 to 3.27.6
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 (83da5b7f)
\
N -- N -- N
refs/heads/dependabot/maven/org.assertj-assertj-core-3.27.6 (3d1d6b8e)
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/maven.yml | 7 ++++---
pom.xml | 4 ++--
.../maven/plugins/javadoc/AbstractJavadocMojo.java | 21 ++++-----------------
.../apache/maven/plugins/javadoc/StaleHelper.java | 21 ++-------------------
.../apache/maven/plugins/javadoc/SystemUtils.java | 19 +++++++++++++++++++
5 files changed, 31 insertions(+), 41 deletions(-)
