discard 9024383 test failing build 3.1 + Java 7
add ef3addd Updated testing matrix to include Java 16
add 39b44d2 Bump junit to 4.13.2
add 145ecb5 Bump slf4j to 1.7.29 (tests)
add 15baa63 [MSITE-871] Use Javadoc plugin property
add 7be9340 Bump surefire version to 2.22.2
add 201104c Bump maven-archiver from 3.5.0 to 3.5.1
add 9b58d41 deps: update plexus-archiver to 4.2.4
add 0a662b8 Bump maven-shared-utils from 3.1.0 to 3.3.3
add eeb148b Added Dependabot config
new bf905c5 test failing build 3.1 + Java 7
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 (9024383)
N -- N -- N refs/heads/jenkins (bf905c5)
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 1 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.