[
https://issues.apache.org/jira/browse/GROOVY-8196?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16018970#comment-16018970
]
John Wagenleitner commented on GROOVY-8196:
-------------------------------------------
{quote}What is your motivation to move the class into core?{quote}
Just thought that since it's a single class similar in use to the JUnit runners
already in core, it would be more convenient in core and would eliminate one
artifact (groovy-testng). Since, based on what I can tell, the GroovyRunners
are used as part of GroovyShell to execute classes that it doesn't otherwise
know what to do with, having it as part of the core runners would probably not
significantly impact performance in searching for ways to execute a script.
Mainly just wanted to pose the question, no great need for the change.
> Make TestNG a core GroovyRunner
> -------------------------------
>
> Key: GROOVY-8196
> URL: https://issues.apache.org/jira/browse/GROOVY-8196
> Project: Groovy
> Issue Type: Brainstorming
> Components: groovy-runtime
> Affects Versions: 2.5.0-alpha-1, 2.4.11
> Reporter: John Wagenleitner
> Priority: Minor
>
> The {{TestNgRunner}} in the {{groovy-testng}} subproject uses reflection to
> run tests. It is a simple class with no direct dependencies on testng. This
> {{GroovyRunner}} could be moved into core and the subproject module
> deprecated, and could be added to the RUNNER_REGISTRY in {{GroovySystem}}.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
