Most likely we will have to replace the eager meta class init with a
lazy one to finally get JDK9 stop complaining. In that case we are still
a long way from 3.0
Am 11.12.2017 um 09:28 schrieb Paul King:
3.0 is still some time away from being feature complete.
On Mon, Dec 11, 2017 at 6:26 PM, Ruben Laguna <ruben.lag...@gmail.com
<mailto:ruben.lag...@gmail.com>> wrote:
I see, thank you very much.
I'll take a look at how to implement the methodMissing support since
I'm really interested on having this at some point in Groovy. Is there
any chance to see this in Groovy 3.0 if you receive a satisfactory
patch? or is too late for 3.0?
Best regards/Rubén
On Fri, Dec 8, 2017 at 7:02 PM, Jochen Theodorou <blackd...@gmx.org
<mailto:blackd...@gmx.org>> wrote:
> On 08.12.2017 10:31, Ruben Laguna wrote:
>>
>> I've found the following *old* bug report from 2009:
>>
>> [GROOVY-3867 Allow methodMissing/propertyMissing to be defined
through
>> category |https://issues.apache.org/jira/browse/GROOVY-3867
<https://issues.apache.org/jira/browse/GROOVY-3867>]
>>
>> which says that methodMissing does not work since Groovy 1.6.5.
>
>
> ok, then it is something we never got to fix
>
>> So I've opened a new JIRA ticket [iGROOVY-8408 invokeMethod
cannot be
>> set through
category|https://issues.apache.org/jira/browse/GROOVY-8408
<https://issues.apache.org/jira/browse/GROOVY-8408>]
>
>
> as long as we have the GroovyObject based logic we currently have
> invokeMethod cannot receive this kind of treatment.
>
> bye Jochen
--
/Rubén
