[jira] [Resolved] (GROOVY-8688) AsmDecompiler.parseClass fails against a Java 11 JEP 181 class

Previous Topic Next Topic
 
classic Classic list List threaded Threaded
1 message Options
Reply | Threaded
Open this post in threaded view
|

[jira] [Resolved] (GROOVY-8688) AsmDecompiler.parseClass fails against a Java 11 JEP 181 class

JIRA jira@apache.org

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

Paul King resolved GROOVY-8688.
-------------------------------
       Resolution: Fixed
         Assignee: Paul King
    Fix Version/s: 3.0.0-alpha-4

Proposed PR merged. I have 3.0 as fix version for now. I'll update if merged into 2.5.

> AsmDecompiler.parseClass fails against a Java 11 JEP 181 class
> --------------------------------------------------------------
>
>                 Key: GROOVY-8688
>                 URL: https://issues.apache.org/jira/browse/GROOVY-8688
>             Project: Groovy
>          Issue Type: Bug
>          Components: bytecode
>    Affects Versions: 2.5.0
>            Reporter: Robert Stupp
>            Assignee: Paul King
>            Priority: Major
>             Fix For: 3.0.0-alpha-4
>
>
> If {{AsmDecompiler.parseClass}} is invoked on Java 11 for a class that already uses [nest-based access control|http://openjdk.java.net/jeps/181], parsing with asm (on master) will fail with an {{UnsupportedOperationException}} in {{org.objectweb.asm.ClassVisitor#visitNestMemberExperimental}} or {{visitNestHostExperimental}}.
> A trivial fix is to bump {{org.codehaus.groovy.control.CompilerConfiguration#ASM_API_VERSION}} to {{ASM7_EXPERIMENTAL}} with asm 6.2.
> For the 2.5.x-branch, an upgrade from asm 6.1.1 to 6.2 is necessary.
>  
> [PR for GROOVY_2_5_x branch|https://github.com/apache/groovy/pull/768]
> [PR for master branch|https://github.com/apache/groovy/pull/769]
> {{./gradlew test}} is clean for both branches.
>  
> Side note: I've added the maven plugin to allow deployment of the artifacts into the local maven repo. I suspect, it should to removed from the PRs?



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)