This is an automated email from the ASF dual-hosted git repository.
github-bot pushed a change to branch
dependabot/maven/org.codehaus.plexus-plexus-java-1.5.0
in repository https://gitbox.apache.org/repos/asf/maven-javadoc-plugin.git
discard ad6eff41 Bump org.codehaus.plexus:plexus-java from 1.3.0 to 1.5.0
add f8560f2f Bump org.apache.commons:commons-text from 1.12.0 to 1.13.1
add fb0e820d Bump org.codehaus.plexus:plexus-interactivity-api from 1.3 to
1.4
add c60edbcc deprecate toRelative (#379)
add 149bf9a2 Cure deprecation warning (#383)
add d3fbbda8 Issue #378 Cleanup of code related to old non supported Java
version (#382)
add 2fb9082f Bump org.codehaus.plexus:plexus-java from 1.3.0 to 1.5.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 (ad6eff41)
\
N -- N -- N
refs/heads/dependabot/maven/org.codehaus.plexus-plexus-java-1.5.0 (2fb9082f)
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 | 4 +-
.../plugins/javadoc/AbstractFixJavadocMojo.java | 12 +-
.../maven/plugins/javadoc/AbstractJavadocMojo.java | 152 ++++++---------------
.../maven/plugins/javadoc/JavadocReport.java | 11 +-
.../apache/maven/plugins/javadoc/JavadocUtil.java | 7 +-
.../maven/plugins/javadoc/TestJavadocReport.java | 6 +-
6 files changed, 64 insertions(+), 128 deletions(-)
