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 9811cb4 (doc) tune ci setup
discard 2d11680 Bump assertj-core from 3.19.0 to 3.21.0
discard 5fe5865 Bump commons-io from 2.8.0 to 2.11.0
discard 0bf0571 Bump doxia-site-renderer from 1.9.2 to 1.10
discard 983b4cf Bump doxia-sink-api from 1.9.1 to 1.10
discard ae9ca98 Bump plexus-interactivity-api from 1.0 to 1.1
add bbd1987 Bump actions/cache from 2.1.6 to 2.1.7
add 87e01b5 Bump actions/checkout from 2.3.5 to 2.4.0
add c425119 Bump qdox from 2.0.0 to 2.0.1
add 6720756 Bump mockito-core from 4.0.0 to 4.1.0
add 9c78cd6 (doc) tune ci setup
add c6db7b2 Bump assertj-core from 3.19.0 to 3.21.0
add faf0722 Bump commons-io from 2.8.0 to 2.11.0
new 4c36137 Bump plexus-interactivity-api from 1.0 to 1.1
new ba5624e Bump doxia-sink-api from 1.9.1 to 1.11.1
new c3cab94 Bump doxia-site-renderer from 1.9.2 to 1.10
new 51a2c3f Bump maven-javadoc-plugin to 3.3.1
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 (9811cb4)
\
N -- N -- N refs/heads/next (51a2c3f)
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 4 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 | 11 ++++++++---
1 file changed, 8 insertions(+), 3 deletions(-)
