You are viewing a plain text version of this content. The canonical link for it is here.
Posted to notifications@groovy.apache.org by "Daniel Sun (JIRA)" <ji...@apache.org> on 2019/08/01 14:41:00 UTC

[jira] [Resolved] (GROOVY-9109) Groovysh: Do not force override classloader if user supplied is already GroovyClassLoader

     [ https://issues.apache.org/jira/browse/GROOVY-9109?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Daniel Sun resolved GROOVY-9109.
--------------------------------
       Resolution: Fixed
         Assignee: Daniel Sun
    Fix Version/s: 3.0.0-beta-3
                   2.5.8

The proposed PR was merged. Thanks!

> Groovysh: Do not force override classloader if user supplied is already GroovyClassLoader
> -----------------------------------------------------------------------------------------
>
>                 Key: GROOVY-9109
>                 URL: https://issues.apache.org/jira/browse/GROOVY-9109
>             Project: Groovy
>          Issue Type: Improvement
>          Components: Groovysh
>    Affects Versions: 2.5.6
>            Reporter: Jan Lukavský
>            Assignee: Daniel Sun
>            Priority: Major
>             Fix For: 2.5.8, 3.0.0-beta-3
>
>          Time Spent: 2.5h
>  Remaining Estimate: 0h
>
> When user supplies class loader that is already GroovyClassLoader, Groovysh should use it as it is and do not create another GroovyClassLoader with the user supplied as parent. Reason for this is that user might want to have finer control over generated classes in the groovy shell.



--
This message was sent by Atlassian JIRA
(v7.6.14#76016)