[ 
https://issues.apache.org/jira/browse/GROOVY-8140?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15952764#comment-15952764
 ] 

ASF GitHub Bot commented on GROOVY-8140:
----------------------------------------

GitHub user jwagenleitner opened a pull request:

    https://github.com/apache/groovy/pull/520

    GROOVY-8140: Invoke method not returning MOP super method if isCallTo…

    …Super
    
    See [dev mailing list 
discussion](http://mail-archives.apache.org/mod_mbox/groovy-dev/201703.mbox/%3CCAPbPdObHqPg7aFHSwLf0sRMdHqrRa1vuNwRvxuZVQu5VQ840%2Bw%40mail.gmail.com%3E)

You can merge this pull request into a Git repository by running:

    $ git pull https://github.com/jwagenleitner/groovy groovy8140

Alternatively you can review and apply these changes as the patch at:

    https://github.com/apache/groovy/pull/520.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

    This closes #520
    
----
commit 433eaf8c62f809d531bb9984b126252172f8287c
Author: John Wagenleitner <[email protected]>
Date:   2017-04-02T15:34:47Z

    GROOVY-8140: Invoke method not returning MOP super method if isCallToSuper

----


> Invoke method not returning MOP super method if isCallToSuper
> -------------------------------------------------------------
>
>                 Key: GROOVY-8140
>                 URL: https://issues.apache.org/jira/browse/GROOVY-8140
>             Project: Groovy
>          Issue Type: Bug
>          Components: groovy-runtime
>    Affects Versions: 2.4.8
>            Reporter: John Wagenleitner
>            Priority: Critical
>
> Recent commit 0a6789d06c [1] reintroduced behavior that skips methods for 
> super.  See mailing list discussion [2].
> [1] 
> https://github.com/apache/groovy/commit/0a6789d06cc6451fcfee174ba638c0494f2827ef
> [2] 
> http://mail-archives.apache.org/mod_mbox/groovy-dev/201703.mbox/%3CCAPbPdObHqPg7aFHSwLf0sRMdHqrRa1vuNwRvxuZVQu5VQ840%2Bw%40mail.gmail.com%3E



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

Reply via email to