[ https://issues.apache.org/jira/browse/GROOVY-9292?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16961228#comment-16961228 ]
Daniel Sun commented on GROOVY-9292: ------------------------------------ {quote}Is this an "Access is forbidden" compilation error? Can you explain why enabling dynamic property is the chosen solution {quote} [~emilles] The access forbidden error does not happen while checking type, actually it happens while writing call sites. Enabling the dynamic property can help call site writer to choose a valid approach to write call sites. [https://github.com/apache/groovy/blob/9be48ebff4b9cf31b02dcc7d627ddbcfdaf3d6a8/src/main/java/org/codehaus/groovy/classgen/asm/sc/StaticTypesCallSiteWriter.java#L127] > Compilation error when accessing a protected super class field from a closure > using owner, delegate or thisObject qualifier (different package) > ----------------------------------------------------------------------------------------------------------------------------------------------- > > Key: GROOVY-9292 > URL: https://issues.apache.org/jira/browse/GROOVY-9292 > Project: Groovy > Issue Type: Bug > Components: Static compilation > Affects Versions: 2.5.8, 3.0.0-rc-1 > Reporter: Daniel Sun > Assignee: Daniel Sun > Priority: Major > > Compilation fails when accessing a protected(via `thisObject`, `owner` and > `delegate`)/package-private super class field from inside a closure: > {code:java} > new GroovyShell().with { > evaluate ''' > package a > > abstract class Abstract { > protected String protectedField = 'field' > } > assert true > ''' > evaluate ''' > package b > > @groovy.transform.CompileStatic > class Concrete extends a.Abstract { > String doThing() { > 'something'.with { > return owner.protectedField // `thisObject.protectedField`, > `delegate.protectedField` fails too > } > } > } > assert true > ''' > evaluate 'assert new b.Concrete().doThing() == "field"' > {code} -- This message was sent by Atlassian Jira (v8.3.4#803005)