[
https://issues.apache.org/jira/browse/SUREFIRE-1911?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17467300#comment-17467300
]
Réda Housni Alaoui commented on SUREFIRE-1911:
----------------------------------------------
Here is the associated pull request =>
https://github.com/jenkins-infra/pipeline-library/pull/272
> Groovy-based JUnit 4 tests no longer run w/ 5 in classpath
> ----------------------------------------------------------
>
> Key: SUREFIRE-1911
> URL: https://issues.apache.org/jira/browse/SUREFIRE-1911
> Project: Maven Surefire
> Issue Type: Bug
> Components: Junit 4.x support, Maven Surefire Plugin
> Affects Versions: 3.0.0-M5
> Reporter: Jesse Glick
> Assignee: Tibor Digana
> Priority: Major
> Labels: regression
>
> Using Maven 3.8.1 and JDK 8,
> https://github.com/jenkins-infra/pipeline-library/commit/48fc69bdd3f7e3adbebea76b8bf68edfe5ed3e32
> causes {{mvn test}} to not do anything:
> {code:none}
> Tests run: 0, Failures: 0, Errors: 0, Skipped: 0
> {code}
> In 3.0.0-M3, or for that matter 3.0.0-M4, this runs a variety of tests as
> expected. {{git bisect}} points to the fix of SUREFIRE-1787 as the culprit:
> {code:none}
> d5bbb3f9ae37ff5ad2bb7e8b3c11d1f24ea6f041 is the first bad commit
> commit d5bbb3f9ae37ff5ad2bb7e8b3c11d1f24ea6f041
> Author: tibordigana <[email protected]>
> Date: Sat May 2 13:08:16 2020 +0200
> [SUREFIRE-1787] Support multiple runners (JUnit4, TestNG, other) and
> their API in JUnit5 Provider
> {code}
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
