Jaikiran

Hello @azotcsit, the `listener` element is meant to allow any kind of listener implementations as long as they implement the JUnit 5 platform's API `org.junit.platform.launcher.TestExecutionListener`. As such the current `resultFile`...

this is ok to test

Hi @reudismam, Is there some reference documentation which states that this construct performs better? My brief check of the JLS just showed a note which states that some implementations _might_...

Thank you for creating this PR. Looks like our CI hasn't been picking up PR related runs. I'll run some tests manually and see how it goes.

Hello @mguillem, please give me a few days on this one. I have tested this locally and do see some issues with the changes (not that we won't be able...

Hello @mguillem, sorry to keep you waiting and thank you for the patience. Here's more details on why I used `legacyReportingName` when I fixed https://bz.apache.org/bugzilla/show_bug.cgi?id=63680 and why the current proposed...

> alternative: add an option to the JUnitLauncher task to specifiy which name should be used Yes, I had this in mind but hadn't seen a necessity yet. But I...

> @mguillem @jaikiran What needs to be done to see this issue fixed? Can we help? Hello @don-vip, I think allowing the users to (optionally) decide which name to display...

I've pushed a commit[1] which adds support to configure which style of names are used for reporting. More specifically, the `listener` nested element of the `junitlauncher` can now be set...

Hello @don-vip, we do publish our nightly builds[1], so if you want to give this a try before we do an official release (no date set yet), then please use...