[
https://issues.apache.org/jira/browse/GROOVY-8197?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16020506#comment-16020506
]
Paul King commented on GROOVY-8197:
-----------------------------------
Conceptually, they should become part of RUNNER_REGISTRY. Historically, because
of {{GroovyTestCase}} having a hard dependency on JUnit classes, we've always
bundled JUnit in the distribution. We'd just need to ensure none of that broke
when we did the change. It would pave the way for a future version of Groovy
that might for instance focus on JUnit5 (or indeed a core with no testing that
might be good for embedded scenarios).
> Make JUnit3/4 GroovyRunners
> ---------------------------
>
> Key: GROOVY-8197
> URL: https://issues.apache.org/jira/browse/GROOVY-8197
> Project: Groovy
> Issue Type: Brainstorming
> Components: groovy-runtime
> Affects Versions: 2.5.0-alpha-1, 2.4.11
> Reporter: John Wagenleitner
> Priority: Minor
>
> Current {{GroovyShell}} currently has reflective methods to detect and run
> JUnit3 and JUnit4 classes. These methods might work god as {{GroovyRunner}}
> classes and they could be added to the RUNNER_REGISTRY in {{GroovySystem}}.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
