You are viewing a plain text version of this content. The canonical link for it is here.
Posted to notifications@groovy.apache.org by "John Wagenleitner (JIRA)" <ji...@apache.org> on 2018/06/25 14:25:00 UTC
[jira] [Resolved] (GROOVY-8649) Class loading in Groovy 2.5 breaks
class loading hierarchy
[ https://issues.apache.org/jira/browse/GROOVY-8649?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
John Wagenleitner resolved GROOVY-8649.
---------------------------------------
Resolution: Not A Bug
Assignee: John Wagenleitner
> Class loading in Groovy 2.5 breaks class loading hierarchy
> ----------------------------------------------------------
>
> Key: GROOVY-8649
> URL: https://issues.apache.org/jira/browse/GROOVY-8649
> Project: Groovy
> Issue Type: Bug
> Components: class generator
> Affects Versions: 2.5.0
> Reporter: Alexander Veit
> Assignee: John Wagenleitner
> Priority: Blocker
>
> Prior to Groovy 2.5 GroovyClassLoader passed classes requested by script code like
> {quote}def obj = new org.example.NonScriptableClass(){quote}
> to its parent class loader (hereby the NonScriptableClasses are Java classes).
> We use this behavior to allow or deny loading of Java classes with the parent class loader based on certain annotations on the respective class.
> With Groovy 2.5 this behavior has changed. org.example.NonScriptableClass is no more passed to the parent class loader. This breaks our security mechanism.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)