maven-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
Subject [maven-surefire] branch junit5-displayname updated (b52122d -> 5f6e1bd)
Date Sun, 27 Jan 2019 06:42:40 GMT
This is an automated email from the ASF dual-hosted git repository.

tibordigana pushed a change to branch junit5-displayname
in repository

 discard b52122d  added version JUnit5 Platform 1.4.0-RC1 in JUnitPlatformEnginesIT
 discard f60dd66  JUnit5 Vintage 5.3.2 in documentation
 discard 329b70c  Upgrade jacoco-maven-plugin:0.8.3
 discard d51a09c  [SUREFIRE-1546] JUnit 5 runner does not honor JUnit 5 display names
     new 001e807  [SUREFIRE-1546] JUnit 5 runner does not honor JUnit 5 display names
     new 5f6e1bd  Upgrade jacoco-maven-plugin:0.8.3

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   (b52122d)
             N -- N -- N   refs/heads/junit5-displayname (5f6e1bd)

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 2 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:
 .../jiras/   |  6 +++---
 .../maven/surefire/junitplatform/     | 12 ++++++------
 .../maven/surefire/junitplatform/ |  6 +++---
 3 files changed, 12 insertions(+), 12 deletions(-)

View raw message