You are viewing a plain text version of this content. The canonical link for it is here.
Posted to notifications@groovy.apache.org by "Paul King (Jira)" <ji...@apache.org> on 2020/01/26 23:50:00 UTC

[jira] [Updated] (GROOVY-4490) Method Chaining + invokeMethod

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

Paul King updated GROOVY-4490:
------------------------------
    Fix Version/s:     (was: 2.5.x)
                       (was: 3.x)

> Method Chaining + invokeMethod
> ------------------------------
>
>                 Key: GROOVY-4490
>                 URL: https://issues.apache.org/jira/browse/GROOVY-4490
>             Project: Groovy
>          Issue Type: Sub-task
>          Components: Compiler
>    Affects Versions: 1.7.4
>         Environment: Using the latest groovy-eclipse version, 2.1.0
>            Reporter: Mike Goodwin
>            Priority: Major
>         Attachments: regression1.7.1-1.7.4-2.zip, regression1.7.1-1.7.4.zip, t.groovy
>
>
> This bug has been introduced somewhere between 1.7.0 (the old groovy eclipse plugin, where it worked) & 1.7.4
> I do not have a test case, but the issue seems to be with method chaining.
> proxyObj.getX().getY()
> What happens is getY() is run on the proxyObj. Presumably it method chaining should work only when the return type is void, and in this case it is confused because the return type is not as obvious.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)