This is an automated email from the ASF dual-hosted git repository.
slachiewicz pushed a change to branch next
in repository https://gitbox.apache.org/repos/asf/maven-javadoc-plugin.git.
discard 86fb593 Added Java 16 and 17 to Github Action tests
discard 9d1aaa5 Tests improvements / AssertJ / Java 16+
new 5085ee5 Added Java 16 and 17 to Github Action tests
new 5aeb37d Tests improvements / AssertJ / Java 16+
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 (86fb593)
\
N -- N -- N refs/heads/next (5aeb37d)
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.
The 2 revisions listed above as "new" are entirely new to this
repository and will be described in separate emails. The revisions
listed as "add" were already present in the repository and have only
been added to this reference.
Summary of changes:
pom.xml | 5 +
src/it/projects/MJAVADOC-172/verify.bsh | 2 +-
.../maven/plugins/javadoc/JavadocReportTest.java | 521 +++++++++++----------
.../maven/plugins/javadoc/JavadocUtilTest.java | 35 +-
4 files changed, 275 insertions(+), 288 deletions(-)
