Details
-
Bug
-
Status: Closed
-
Major
-
Resolution: Not A Bug
-
2.19, 2.19.1, 2.20
-
None
-
None
Description
I've verified the same scenario with 2.18, 2.19 and 2.20 versions of the plugin.
It looks like the issue was introduced in 2.19.
I'd kindly like to ask to fix this as soon as possible, as this is a blocker in adopting JUnit5!
Steps to reproduce:
- Have a simple project with at least two tests
- Configure
forkCount=2
- Configure workingDirectory, eg.
${project.basedir}/target/test-run
- Run
mvn clean test -T 2
- Observe the exception (might occur randomly)
I'm attaching the error message, full stack trace, and my example pom.xml, that I used to reproduce the issue.