This is an automated email from the ASF dual-hosted git repository.

github-bot pushed a change to branch dependabot/maven/mvnversion-3.9.9
in repository https://gitbox.apache.org/repos/asf/maven-dist-tool.git


    omit 64b95ed  Bump mvnversion from 3.2.5 to 3.9.9
     add f36cb60  Improve jenkins build
     add ef76398  Report a check errors as unit integration test
     add 3d97f7c  Bump mvnversion from 3.2.5 to 3.9.9

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   (64b95ed)
            \
             N -- N -- N   refs/heads/dependabot/maven/mvnversion-3.9.9 
(3d97f7c)

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:
 Jenkinsfile                                        |  34 +++++--
 pom.xml                                            |  38 ++------
 .../maven/dist/tools/DistCheckErrorsReport.java    | 104 ++++++++++-----------
 .../maven/dist/tools/DummyFailureReport.java       |  68 --------------
 .../maven/dist/tools/CheckReportResultIT.java      |  53 +++++++++++
 5 files changed, 131 insertions(+), 166 deletions(-)
 delete mode 100644 
src/main/java/org/apache/maven/dist/tools/DummyFailureReport.java
 create mode 100644 
src/test/java/org/apache/maven/dist/tools/CheckReportResultIT.java

Reply via email to