[
https://issues.apache.org/jira/browse/GROOVY-9005?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16773236#comment-16773236
]
Devin Rosenbauer commented on GROOVY-9005:
------------------------------------------
I will give it a try. Unfortunately, my actual inner class isn't a Callable,
but rather an application-specific Command class with more than one method that
can be overridden. I could potentially figure out a way to use the "single
abstract method" syntax, but I'd rather it work correctly!
I was able to work around the issue for now by converting the immediate
superclass to Groovy and/or not using CompileStatic in certain areas. The
application has a mixed set of classes because I converted it from a Java
project to a Groovy project partway through development. What's Java and what's
Groovy mainly depends on age.
> SomeClass.groovy: -1: Access to java.lang.Object#this is forbidden @ line -1,
> column -1
> ---------------------------------------------------------------------------------------
>
> Key: GROOVY-9005
> URL: https://issues.apache.org/jira/browse/GROOVY-9005
> Project: Groovy
> Issue Type: Bug
> Components: Static compilation
> Affects Versions: 2.5.6
> Reporter: Devin Rosenbauer
> Priority: Major
> Attachments: GROOVY-9005.zip
>
>
> I'm receiving the above error when attempting to compile certain classes that
> have @CompileStatic on either the class or a method within a dynamically
> compiled class. The project is a cross-compiled Java / Groovy project with
> all classes of both types defined in the "groovy" structure. The error can be
> reproduced when a Groovy class extends a Java class which extends a Groovy
> class, then a method in the Java class is called from an inner class of the
> Groovy class.
> The simplest case I can derive to reproduce the failure is attached.
> A is the class which fails to compile. A1 and A2 are the Java and Groovy
> superclasses, respectively.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
