(maven-surefire) branch doxia-2.0.0 updated (455a9197e -> 2f14a7ee1)

[mi...@apache.org]

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-surefire.git


 discard 455a9197e [SUREFIRE-2227] Dynamically calculate xrefTestLocation
 discard 83bbbb100 [SUREFIRE-2228] Upgrade to Doxia 2.0.0 Milestone Stack
 discard 1fdf546de [SUREFIRE-2161] Align Mojo class names and output names
     add 4648b4740 add Reproducible Builds badge
     add 79ea7178a [SUREFIRE-2256] Upgrade to Parent 43
     add 1830625ce [SUREFIRE-2161] Align Mojo class names and output names
     add 1110b988f [SUREFIRE-2228] Upgrade to Doxia 2.0.0 Milestone Stack
     add 2f14a7ee1 [SUREFIRE-2227] Dynamically calculate xrefTestLocation

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   (455a9197e)
            \
             N -- N -- N   refs/heads/doxia-2.0.0 (2f14a7ee1)

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.

No new revisions were added by this update.

Summary of changes:
 README.md                              |  1 +
 pom.xml                                |  3 ++-
 src/config/checkstyle-suppressions.xml | 29 +++++++++++++++++++++++++++++
 3 files changed, 32 insertions(+), 1 deletion(-)
 create mode 100644 src/config/checkstyle-suppressions.xml