Investigating bug #206441 I found that maven.junit had to simply copy numerous node classes from junit, with the predictable subtle differences in behavior. The reason is that org.netbeans.modules.junit.output hardcodes support for Ant sessions but also includes the standard test node implementations, tied to the Ant implementation. I consider this an architectural defect.
You need to make JUnitTestRunnerNodeFactory into some kind of friend API that maven.junit can reuse, so that it need only supply JUnitOutputProcessorFactory (+ JUnitOutputListenerProvider) and perhaps a few minor customizations; then factor JUnitAntLogger and related classes in org.netbeans.modules.junit.output, plus all of org.netbeans.modules.junit.output.antutils, into a new module junit.ant (removing the o.apache.tools.ant.module dep from junit itself).
This will also be useful for permitting an alternate JavaRunner.QUICK_TEST impl based on extexecution rather than Ant.