Olivier Lamy

issue introduced with 3.0.0-M5 culprit c5319bf493c2929d13cd62d89c34704d5d5cb33a

> @olamy Can you link the reproducer? sure have a look here https://github.com/jetty-project/servlet-tck-run/ use branch `jetty-12-ee11-parallel-test` `mvn clean verify` you may have a lot of download of snapshots, you will...

> Overall I think this is a good idea to make Arquillian more thread-safe. However, I do think it will be quite a task to do so. Yup I agree...

oh yup sure. Sorry I didn't reallly look deeply into it but definitely sounds like more big changes to `ArrayList` to `CopyOnWriteArrayList`

> Does it mean that [Using POJO Tests](https://maven.apache.org/surefire/maven-surefire-plugin/examples/pojo-test.html) would also go? I'm not sure - but I think JU3 is used for that. sure will be removed as well see...

> JUnit 3 still works and is still widely used, including in some of Maven's own code. This just seems likely t impose a lot of needless churn on users....

@elharo In that case, nothing prevents you from using pluginManagement to enforce the last version of the Surefire plugin that still supports this setup. Since users relying on such configurations...

Please note junit 3.x code is still supported but junit version as dependency needs to be at least 4.12 it's only the proprieraty surefire runner code which is removed

not sure to understand if you are not using this property in your pom you should not see this warning. so the warning means you are still using it in...

you should be able to override the dependency by adding it in the dependencies section of the plugin itself.