This is an automated email from the ASF dual-hosted git repository.
tibordigana pushed a change to branch TLS1.2
in repository https://gitbox.apache.org/repos/asf/maven-surefire.git.
discard 02d4efb surefire-grouper does not require prerequisites
discard 60dd4b8 fixed CheckTestNgListenerReporterIT with
org.testng:testng:7.0.0-beta7
discard f47d616 TLS 1.2 passed to maven-invoker-plugin via system property
new 41e589f fixed CheckTestNgListenerReporterIT with
org.testng:testng:7.0.0-beta7
new a1f8fe9 surefire-grouper does not require prerequisites
new 1f067c6 TLS 1.2 passed to maven-invoker-plugin via system property
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 (02d4efb)
\
N -- N -- N refs/heads/TLS1.2 (1f067c6)
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:
Jenkinsfile | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
