[
https://issues.apache.org/jira/browse/SUREFIRE-1307?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15710266#comment-15710266
]
ASF GitHub Bot commented on SUREFIRE-1307:
------------------------------------------
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.
> Provide a convenient way to run tests against multiple JUnit versions
> ---------------------------------------------------------------------
>
> Key: SUREFIRE-1307
> URL: https://issues.apache.org/jira/browse/SUREFIRE-1307
> Project: Maven Surefire
> Issue Type: Test
> Reporter: Benedikt Ritter
> Assignee: Tibor Digana
> Fix For: junit5
>
>
> In order to make sure all feature that where working with the JUnit 4
> proivder, we need a way to execute the JUnit 4 integration tests also against
> the JUnit 5 provider.
> Provide a convenient way to execute existing tests against multiple JUnit
> versions.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
