[
https://issues.apache.org/jira/browse/GROOVY-10582?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17523060#comment-17523060
]
Paul King commented on GROOVY-10582:
------------------------------------
Thinking about this some more, I believe you are right that this isn't the way
to go. The original motivation for this issue was threefold:
# Trying to do some refactoring to minimise future work handling the JEP-411
deprecation in fewer places.
# Trying to remove the warnings which are currently shown in recent JDKs
# Providing a graceful fallback when eventually some of the related methods
throw UnsupportedOperationException as foreshadowed in JEP-411.
Other projects[1][2] have stop gap solutions for minimising warnings. I am not
sure if we can borrow some of that idea. There is no public method in their
solution which would be our problem.
It might be that we can cover off the graceful fallback better using a runtime
version check before calling such methods and perhaps for Groovy 5 we remove
all security related API calls entirely. I'll bring that up on the mailing list.
[1] https://github.com/elastic/elasticsearch/pull/80462/files
[2] https://github.com/elastic/elasticsearch/issues/80344
> Funnel checkPermission through VMPlugin (JEP-411)
> -------------------------------------------------
>
> Key: GROOVY-10582
> URL: https://issues.apache.org/jira/browse/GROOVY-10582
> Project: Groovy
> Issue Type: Sub-task
> Reporter: Paul King
> Assignee: Paul King
> Priority: Major
>
> We can reduce our exposure to JEP-411 by funnelling calls to
> SecurityManager#checkPermission through the VMPlugin.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
