[
https://issues.apache.org/jira/browse/GROOVY-5471?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15833655#comment-15833655
]
John Wagenleitner commented on GROOVY-5471:
-------------------------------------------
{quote}Just commenting on this issue, this is a more general problem for indy,
which is also how to run tests while being sure that indy is on despite they
use things like assertScript.{quote}
It looks like since this comment [commit
40b02bca|https://github.com/apache/groovy/commit/40b02bcadce3c3d0768bcc35b3920f04322ea004]
added the {{groovy.target.indy}} System property to provide a mechanism to
ensure indy is enabled for such things as {{assertScript}}.
> Add "indy" option to Groovy Console
> -----------------------------------
>
> Key: GROOVY-5471
> URL: https://issues.apache.org/jira/browse/GROOVY-5471
> Project: Groovy
> Issue Type: Bug
> Components: Groovy Console
> Affects Versions: 2.0-beta-3
> Reporter: Cédric Champeau
>
> If "invokedynamic" support is available, the groovy console should show an
> option allowing the scripts written in the console to be compiled with indy
> support too.
> Otherwise, the user might think that because he's using a "indy" jar, the
> Groovy Console will compile scripts with indy activated, but in reality, only
> core groovy classes will use indy.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
