[
https://issues.apache.org/jira/browse/GROOVY-10145?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17469249#comment-17469249
]
Chad Wilson commented on GROOVY-10145:
--------------------------------------
While trying to migrate a Groovy-based Gradle build to run under Java 17 I am
struggling bit with a common support library (Grolifant) that is failing with
errors that look a lot like GROOVY-10137 or GROOVY-10138.
{code:java}
java.lang.IllegalAccessException: module jdk.proxy11 does not open jdk.proxy11
to unnamed module @458ad742{code}
Abridged stack trace:
{code:java}
at jdk.proxy11/jdk.proxy11.$Proxy109.verify(Unknown Source)
at
org.ysb33r.grolifant.api.v4.downloader.ArtifactDownloader$DownloadAction.call(ArtifactDownloader.groovy:192)
at
org.ysb33r.grolifant.api.v4.downloader.ArtifactDownloader$DownloadAction.call(ArtifactDownloader.groovy)
{code}
Seems to be a dynamic proxy being implemented for
[https://gitlab.com/ysb33rOrg/grolifant/-/blob/master/grolifant40/src/main/groovy/org/ysb33r/grolifant/api/v4/downloader/ArtifactRootVerification.java]
In lieu of a backport, is there any workaround/hack that I might be able to
suggest to the plugin support library author (or apply myself) since Gradle
7.3.3 runs on Groovy 3.0.9? I'm not even sure how I am best to manually open
modules for access by unnamed modules since the dynamic proxies seem to also
have dynamic module names and my understanding is you must open by name given
--illegal-access=permit was dropped in Java 17.
> 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)
