[
https://issues.apache.org/jira/browse/GROOVY-10145?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17472480#comment-17472480
]
Chad Wilson commented on GROOVY-10145:
--------------------------------------
OK, that's a shame. Do you think it'd be possible to clarify the specific
problems for those whom the source code is a bit difficult to make sense of? Is
it *all* Groovy-generated dynamic proxies that are affected (and will end up
inaccessible by the creating module), or do they perhaps have to have specific
characteristics in the interface (e.g types, presence of default methods). I'm
wondering what the minimal workarounds might be for those who need to/wish to
maintain Groovy 3 compatibility.
I'm not sure how long it will practically take Gradle, for instance, to bundle
Groovy 4. It took a very long to get from 2.5 to 3, IIRC - although perhaps the
next one will be easier.
> Support JDK16
> -------------
>
> Key: GROOVY-10145
> URL: https://issues.apache.org/jira/browse/GROOVY-10145
> Project: Groovy
> Issue Type: Bug
> Reporter: Daniel Sun
> Assignee: Daniel Sun
> Priority: Major
> Fix For: 4.0.0-beta-1
>
> Time Spent: 0.5h
> Remaining Estimate: 0h
>
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
