From 8e4bdfbc4542b37b989e632ccb1315bf32495439 Mon Sep 17 00:00:00 2001
From: Valery Kharseko <vharseko@3a-systems.ru>
Date: Mon, 03 Aug 2026 07:56:30 +0000
Subject: [PATCH] [#801] Drop the rerunFailingTestsCount setting that never applied to TestNG (#804)
---
opendj-server-legacy/pom.xml | 10 +++++++++-
1 files changed, 9 insertions(+), 1 deletions(-)
diff --git a/opendj-server-legacy/pom.xml b/opendj-server-legacy/pom.xml
index d0bab44..23e0980 100644
--- a/opendj-server-legacy/pom.xml
+++ b/opendj-server-legacy/pom.xml
@@ -1281,7 +1281,15 @@
<forkCount>1</forkCount>
<parallel>none</parallel>
<runOrder>alphabetical</runOrder>
- <rerunFailingTestsCount>3</rerunFailingTestsCount>
+ <!--
+ No <rerunFailingTestsCount> here on purpose. These tests run with the TestNG
+ provider, which ignores that option: up to and including surefire/failsafe 3.5.x
+ it is implemented by the JUnit 4/5 providers only (SUREFIRE-2134 is still open).
+ Nothing was ever rerun here - neither plain @Test methods nor @DataProvider
+ driven ones - so the setting only looked like a safety net, see issue #801.
+ It starts working with surefire 3.6.0, where TestNG is executed through the
+ unified JUnit Platform provider; moving to it is a migration of its own.
+ -->
</configuration>
</execution>
</executions>
--
Gitblit v1.10.0