[junitlauncher] - Switch back to issuing a separate LauncherDiscoveryRequest for each of the test class that are selected by the <testclass…
[junitlauncher] - Switch back to issuing a separate LauncherDiscoveryRequest for each of the test class that are selected by the <testclasses> usageIn 1.10.5 version (the latest released) of Ant, we used to launchmultiple LauncherDiscoveryRequest (a JUnit 5 construct), one eachfor a test class, that belonged to the <testclasses> usage. Commit3f806148c3f3542b8526d5f91f10d6189bf0607d changed it to launch onesingle LauncherDiscoveryRequest (and including all those testclasses in that request) because it seemed more logical to do so.However, recent tests/experimentation of the master branch hasshown that it introduces complexities when the "legacy-xml"listener (the one which supports generating test results in xmlformat that junitreport understands) is used. These complexitiesinclude - expecting each test class to have a separate report file,but isn't limited to that. Solving these issues isn't easy andprobably not worth it, given that the only reason we started usinga single LauncherDiscoveryRequest is because it just seemed logicaland there is no other strong reason to do so. This commit switchesback to the behaviour that's been there in 1.10.5 version, to issuemultiple separate LauncherDiscoveryRequest(s) one each for thetest class that's selected through the use of <testclasses>.