[
https://issues.apache.org/jira/browse/GROOVY-8197?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16062092#comment-16062092
]
ASF GitHub Bot commented on GROOVY-8197:
----------------------------------------
GitHub user jwagenleitner opened a pull request:
https://github.com/apache/groovy/pull/564
GROOVY-8197: Make JUnit3/4 GroovyRunners
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/jwagenleitner/groovy 8197-groovyrunners
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/groovy/pull/564.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #564
----
commit 469f0e970999e84d1e878801ac56b22af73b9cbf
Author: John Wagenleitner <[email protected]>
Date: 2017-06-09T22:41:38Z
GROOVY-8197: Make JUnit3/4 GroovyRunners
----
> 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}}.
> Runners should be able to be registered during class loading (like most other
> things) rather than during Grape processing.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
