Github user Tibor17 commented on the issue:
https://github.com/apache/maven-surefire/pull/135
@britter
It is not the right way to detect the presents of the JUnit annotations in
classpath because the test classes may initialize static context yet in Maven
process like we do right now which should be avoided in the future.
The Maven and this plugin resolved dependencies. I think this is the way to
go and we should detect the presents of JUnit artifacts and run the appropriate
engine or provider.
It already works like this with JUnit 4+ or 4.7+ and TestNG versions.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at [email protected] or file a JIRA ticket
with INFRA.
---
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
