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

olamy pushed a change to branch multithread-build-possible
in repository https://gitbox.apache.org/repos/asf/maven-surefire.git


 discard 6ecda1963 only one thread to avoid flaky tests and fix path of log4j 
logs to be in target directory
 discard 383724ed7 test Verifier using embedded/auto mode
 discard 2d6cdf427 fix merge
 discard c55a9cd6e fix typo
 discard a8295bfeb surefire-its should depend on all providers
 discard 0d53d83e2 add junit platform provider as well
 discard 562a54f89 wrong merge
 discard 5344fd485 no need of extraArtifacts
 discard 27c5900c7 try to get plugins installed locally so we can have verify 
working, ideally we should use a different local repo
 discard 92efe7100 maven-surefire-report-plugin need as well
 discard c873d91e2 try -T3 for Jenkins and gh
 discard 74c69923a try to include those dependencies to fake the build plan and 
be sure its are runned last when using -Txx or mvnd
     add 7eca0a897 Bump assertj-core from 3.22.0 to 3.23.1
     add ae4bb0fc1 try to include those dependencies to fake the build plan and 
be sure its are runned last when using -Txx or mvnd
     add bf879c698 try -T3 for Jenkins and gh
     add ee58b97cc maven-surefire-report-plugin need as well
     add cec74763e try to get plugins installed locally so we can have verify 
working, ideally we should use a different local repo
     add 9b6b084d8 no need of extraArtifacts
     add 455797e3f wrong merge
     add c7232c5a1 add junit platform provider as well
     add 000864e84 surefire-its should depend on all providers
     add 8272164e5 fix typo
     add 578fff8d9 fix merge
     add 71a11ce41 test Verifier using embedded/auto mode
     add 6cdeb1f82 only one thread to avoid flaky tests and fix path of log4j 
logs to be in target directory

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   (6ecda1963)
            \
             N -- N -- N   refs/heads/multithread-build-possible (6cdeb1f82)

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:
 pom.xml | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

Reply via email to