You are viewing a plain text version of this content. The canonical link for it is here.
Posted to notifications@groovy.apache.org by "Jason Plurad (JIRA)" <ji...@apache.org> on 2016/03/07 20:50:40 UTC

[jira] [Commented] (GROOVY-7562) imports and custom class defs not working in Groovysh Interpreter Mode

    [ https://issues.apache.org/jira/browse/GROOVY-7562?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15183566#comment-15183566 ] 

Jason Plurad commented on GROOVY-7562:
--------------------------------------

Was there a particular reason why the fix wasn't targetted for Groovy 2.4.x?

> imports and custom class defs not working in Groovysh Interpreter Mode
> ----------------------------------------------------------------------
>
>                 Key: GROOVY-7562
>                 URL: https://issues.apache.org/jira/browse/GROOVY-7562
>             Project: Groovy
>          Issue Type: Bug
>          Components: Groovysh
>    Affects Versions: 2.4.0, 2.4.1, 2.4.2, 2.4.3, 2.4.4
>            Reporter: Thibault Kruse
>             Fix For: 2.5.0-beta-1
>
>
> To reproduce
> {code}
> groovy:000> :set interpreterMode true
> groovy:000> class Me { String name }
> ===> true
> groovy:000> m = new Me()
> script14405523893121089774169.groovy: 2: unable to resolve class Me 
> groovy:000> import java.rmi.Remote
> ===> java.rmi.Remote
> groovy:000> Remote x
> script1440757530265448239810.groovy: 1: unable to resolve class Remote 
>  @ line 1, column 8.
>    Remote x
> {code}
> See https://github.com/apache/incubator-groovy/pull/100 for fix



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)