[
https://issues.apache.org/jira/browse/GROOVY-1721?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jochen Theodorou resolved GROOVY-1721.
--------------------------------------
Resolution: Fixed
Assignee: Jochen Theodorou
Fix Version/s: (was: 3.0)
current plans are to not have custom meta classes anymore and instead customize
the existing one. As such the issue here would then be more in a startup script
of an application instead of an automatic lookup, thus I close the issue.
Please reopen if somebody thinks different
> Discovery mechanism for customizing metaclasses with a script using
> ExpandoMetaClass
> ------------------------------------------------------------------------------------
>
> Key: GROOVY-1721
> URL: https://issues.apache.org/jira/browse/GROOVY-1721
> Project: Groovy
> Issue Type: Sub-task
> Components: groovy-runtime
> Reporter: Guillaume Delcroix
> Assignee: Jochen Theodorou
>
> Currently, it is possible to define custom MetaClasses at load time by
> following the convention:
> groovy.runtime.metaclass.java.lang.StringMetaClass
> Creating this StringMetaClass in this specific place will use this metaclass
> in lieu of the default metaclass.
> By adding ExpandoMetaClass back in Groovy, we should provide a mechanism for
> customizing metaclasses.
> For instance, we could create an expandoMetaClassScript.groovy in the package
> groovy.runtim.metaclass.
> And in this script, we would use ExpandoMetaClasses to customize classes
> behaviour further.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
