This is an automated email from the ASF dual-hosted git repository.
michaelo pushed a change to branch doxia-2.0.0
in repository https://gitbox.apache.org/repos/asf/maven-javadoc-plugin.git
discard 47580a90 MSHARED-1327
discard 3e631638 Align plugin with AbstractMavenReport
discard b3b0605d Prepare for Doxia 2.0.0
new 904bce77 Prepare for Doxia 2.0.0
new 95962799 Align plugin with AbstractMavenReport
new 21721ee5 MSHARED-1327
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 (47580a90)
\
N -- N -- N refs/heads/doxia-2.0.0 (21721ee5)
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 3 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:
src/it/mrm/3rdparty/_doclet-1.0.jar | Bin 1542 -> 0 bytes
src/it/mrm/repository/_mjavadoc450-static.jar | Bin 858 -> 0 bytes
2 files changed, 0 insertions(+), 0 deletions(-)
delete mode 100644 src/it/mrm/3rdparty/_doclet-1.0.jar
delete mode 100644 src/it/mrm/repository/_mjavadoc450-static.jar
