JUnit5 resource matching results in inconsistent exceptions

Preconditions:

- A test runner with multiple pdsl test params
- 2 feature files
- 2 parsers, each of which can only recognize one feature file

Steps to Reproduce:

Use *.feature to match files

Expected Results:

The parsers each execute on what they're able to, ignoring everything else

Actual Results:

Exception with error about empty test specifications.
While it is true some files are completely unrecognized, if the feature files are explicitly both listed the framework operates without issue which should be functionally equivalent to *.feature.