This is an automated email from the ASF dual-hosted git repository.
tibordigana pushed a change to branch SUREFIRE-1733
in repository https://gitbox.apache.org/repos/asf/maven-surefire.git.
discard f0adf73 impl jvm args
discard 0cca74b [GH] Workflows j13
discard bcaaeb3 IT failed on j7 and j8 because requires j9+
discard 83d8450 adjusted Surefire1712ExtractedModulenameWithoutASMIT
discard 06571ad [SUREFIRE-1733] Surefire and Failsafe JPMS additions for
JUnit 5.x execution
new 265d7cf [SUREFIRE-1733] Surefire and Failsafe JPMS additions for
JUnit 5.x execution
new 980d58a adjusted Surefire1712ExtractedModulenameWithoutASMIT
new d60b0db IT failed on j7 and j8 because requires j9+
new efc8e96 [GH] Workflows j13
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 (f0adf73)
\
N -- N -- N refs/heads/SUREFIRE-1733 (efc8e96)
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 4 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:
.../booterclient/ModularClasspathForkConfiguration.java | 12 ------------
1 file changed, 12 deletions(-)
