[SUREFIRE-1911] Groovy-based JUnit 4 tests no longer run w/ 5 in classpath

**[Jesse Glick](https://issues.apache.org/jira/secure/ViewProfile.jspa?name=jglick@netbeans.org)** opened **[SUREFIRE-1911](https://issues.apache.org/jira/browse/SUREFIRE-1911?redirect=false)** and commented

Using Maven 3.8.1 and JDK 8, https://github.com/jenkins-infra/pipeline-library/commit/48fc69bdd3f7e3adbebea76b8bf68edfe5ed3e32 causes `mvn test` to not do anything:

```none
Tests run: 0, Failures: 0, Errors: 0, Skipped: 0
```

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:

```none
d5bbb3f9ae37ff5ad2bb7e8b3c11d1f24ea6f041 is the first bad commit
commit d5bbb3f9ae37ff5ad2bb7e8b3c11d1f24ea6f041
Author: tibordigana
Date: Sat May 2 13:08:16 2020 +0200

[SUREFIRE-1787] Support multiple runners (JUnit4, TestNG, other) and their API in JUnit5 Provider
```

---

**Affects:** 3.0.0-M5

**Issue Links:**
- [SUREFIRE-1787](https://issues.apache.org/jira/browse/SUREFIRE-1787) Support multiple runners (JUnit4, TestNG, other) and their API in JUnit5 Provider
(_**"is caused by"**_)
- [SUREFIRE-1963](https://issues.apache.org/jira/browse/SUREFIRE-1963) Detecting multiple test-frameworks

2 votes, 8 watchers

Reproduce the Jenkins pipeline-library case from commit 48fc69bdd3f7e3adbebea76b8bf68edfe5ed3e32 with Maven 3.8.1, JDK 8, and Surefire 3.0.0-M5, then inspect commit d5bbb3f9ae37ff5ad2bb7e8b3c11d1f24ea6f041 linked to SUREFIRE-1787. Done means Groovy-based JUnit 4 tests are discovered and run instead of reporting zero tests.

Written by the indexing model from the issue text.