SoftwareEntwicklung Beratung Schulung

A coders, hackers heaven.....Hm...I do not think so...

Apache Maven Surefire Plugin Version 2.20 Released

The Apache Maven team is pleased to announce the release of the Apache Maven Surefire Plugin, version 2.20.

The release contains 70 bug fixes. Again we received contributions from the community in form of bug reports and bug fixes.

Thank you and keep them coming!

You should specify the version in your project’s plugin configuration:


or for failsafe:


or for surefire-report:


Release Notes – Maven Surefire – Version 2.20


  • SUREFIRE-725 – Test result output ist sent to System.out instead of using logger
  • SUREFIRE-1198 – Failsafe does not allow to configure the jar file to use
  • SUREFIRE-1216 – TEST-*.xml files generated by Surefire are invalid
  • SUREFIRE-1217 – Differentiate XML schema for failsafe and surefire
  • SUREFIRE-1239 – ExecutionException java.lang.RuntimeException: When writing xml report stdout/stderr (No such file or directory)
  • SUREFIRE-1244 – NumberFormatException in parallel test run with runOrder = failedFirst
  • SUREFIRE-1250 – Regex testcase filtering: exception when hashmark is regex-quoted
  • SUREFIRE-1252 – Tests not being run when using XML suite file with TestNG
  • SUREFIRE-1268 – With JUnit listener, redirectTestOutputToFile is ignored
  • SUREFIRE-1278 – TestNG tests are run with group name that ends with specified group
  • SUREFIRE-1284 – Statistics file should not be determined as (directory of surefire-reports).getParentFile().getParentFile(). It is a problem if report directory is customized. Statistics file should be located in project dir.
  • SUREFIRE-1289 – forkedProcessTimeoutInSeconds should not use ping timer of 10 seconds but 0.1 sec period timer
  • SUREFIRE-1290 – Orphan Fork JVMs should be killed after any previous finished with fatal error
  • SUREFIRE-1295 – JVM crashes in forks do not log the name of the failing test
  • SUREFIRE-1296 – The project build directory should not be determined as (directory of surefire-reports).getParentFile(). It is a problem if report directory is customized.
  • SUREFIRE-1305 – surefire fails on parallel tests when newline character is in test description
  • SUREFIRE-1312 – Classpath containing url special characters with Reflections not working
  • SUREFIRE-1313 – Unify console report result in SurefirePlugin and VerifyMojo
  • SUREFIRE-1315 – Fix stylistic errors in DefaultReporterFactory
  • SUREFIRE-1322 – Surefire and Failsafe should dump critical errors in dump file and console
  • SUREFIRE-1324 – Surefire incorrectly suppresses exceptions when closing resources.
  • SUREFIRE-1333 – Process pending events from forked process after exited and then finish forked Thread.
  • SUREFIRE-1341 – Documentation of configuration parameters in Failsafe should mention IT instead or
  • SUREFIRE-1342 – Acknowledge normal exit of JVM and drain shared memory between processes
  • SUREFIRE-1349 – FreeBSD cross process communication needs to commit stdout data in forked JVM within a synchronized block
  • SUREFIRE-1352 – Dump file [date]-jvmRun[N] – where N should be real fork number
  • SUREFIRE-1354 – Sometimes BYE_ACK command is lost
  • SUREFIRE-1357 – PING scheduler kills JVM in debug mode
  • SUREFIRE-1358 – Directory in Class-Path in manifest of forked jvm ends with two slashes //



  • SUREFIRE-1224 – Improve Code Quality After Sonar Report
  • SUREFIRE-1246 – Surefire + Cobertura: Shutdown of Forked JVM timeouts before all thread ends
  • SUREFIRE-1254 – add color messages
  • SUREFIRE-1260 – Add */ as one of the default include patterns
  • SUREFIRE-1272 – Create better report for AssumptionFailure
  • SUREFIRE-1275 – Test regex patterns should be cached
  • SUREFIRE-1293 – Simplify by using the null object pattern
  • SUREFIRE-1310 – ForkClient should handle only one channel-id
  • SUREFIRE-1317 – Refactoring
  • SUREFIRE-1350 – Upgrade Version of maven-invoker-plugin to 2.0.0
  • SUREFIRE-1356 – ForkClient should distinguish between internal and stream errors


  • SUREFIRE-1223 – Cannot run invoker ITs on Windows with Maven 3.3.1+
  • SUREFIRE-1270 – Upgrade JaCoCo Version to 0.7.7
  • SUREFIRE-1281 – Fix permanently failing Surefire Windows Build
  • SUREFIRE-1282 – Use assumeJavaVersion() in integration tests
  • SUREFIRE-1291 – enable unit tests in surefire-integration-tests and rename Surefire1028UnableToRunSingleTest to *IT
  • SUREFIRE-1311 – JUnit47 provider should not internally parse JUnit Description
  • SUREFIRE-1316 – MVN 3.1.0 minimum in build time
  • SUREFIRE-1318 – Upgrade JaCoCo Version to 0.7.8
  • SUREFIRE-1319 – Upgrade RAT Plugin Version to 0.12
  • SUREFIRE-1320 – Upgrade Sniffer Plugin Version to 1.15
  • SUREFIRE-1321 – Integration tests should be cleaned up before running. Add goal=clean in maven-invoker-plugin.
  • SUREFIRE-1326 – Upgrade maven-shared-utils to 3.2.0.


  • SUREFIRE-1306 – JUnit4RerunFailingTestsIT does not execute with the JUnit version configured in the test
  • SUREFIRE-1308 – Move Surefire1179IT to jiras package
  • SUREFIRE-1332 – SurefireLauncher duplicates functions and breaks build with Maven 3.5.0
  • SUREFIRE-1338 – Integration Tests should avoid using duplicated system properties.
  • SUREFIRE-1351 – Performance unit tests should GC to free limited memory size.
  • SUREFIRE-1353 – Integration tests testing jvm forks should use subprocess and not embedded mode


  • SUREFIRE-1297 – Specify surefire temp directory for run in multiple processes


-The Apache Maven team