Make org.junit.platform.console.tasks.*Listener classes public

[kriegfrj]

I have a project where it would be nice to be able to plug in arbitrary test listeners to get the output that you want.

It would be nice to be able to use the listeners in the console package to optionally produce nicely-formatted test output. Unfortunately, I can't do this easily because the classes are package private, so I have to use reflection if I want to use them.

It seems a pity that JUnit 5 now has all this nice modularity to facilitate plug-and-play code re-use like this, but the opportunity to re-use it is thwarted by hiding it away in a private package.

[kriegfrj]

Having played with it a little bit, I think it would also be nice if all the listener-related code were put in a different package to the executor code. I'm looking at an OSGi-type usage of it, and having this separation of packages would make it easier to manage the package dependencies.

[sbrannen]

Tentatively slated for 5.6 M1 for team discussion

[sormuras]

Iirc, we introduced the "reporting" module to contain such public listeners.

[marcphilipp]

Team Decision: Let's polish the listeners to keep the public API small and move them to the reporting module.

[marcphilipp]

@kriegfrj Would you like to submit a PR?

[kriegfrj]

I'll see if I can have a look next week some time. Can't promise anything. I have another couple of suggestions from my experience in trying to use the LegacyXmlGeneratingListener too which might tie in (eg, perhaps org.unit.platform.launcher.listeners.LegacyReportingUtils also belongs in the reporting module and in a different package.