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-reporting-exec.git
discard 23c1f16 Prepare for Doxia 2.0.0
new 3ad6a15 Update CI URL
new 79a7f8d Drop $Id$
new 6e07243 Drop obsolete Maven Central mirror
new 5efd9f1 Drop unused logger
new cc9f23a Improve site.xml
new 1d0ae53 Rest
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 (23c1f16)
\
N -- N -- N refs/heads/doxia-2.0.0 (1d0ae53)
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 6 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:
.../java/org/apache/maven/reporting/exec/MavenReportExecution.java | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
