You are viewing a plain text version of this content. The canonical link for it is here.

Posted to notifications@groovy.apache.org by "Paul King (Jira)" <ji...@apache.org> on 2022/04/15 06:21:00 UTC

[jira] [Updated] (GROOVY-10581) Prepare for deprecation of security manager (JEP-411)

     [ https://issues.apache.org/jira/browse/GROOVY-10581?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Paul King updated GROOVY-10581:
-------------------------------
    Summary: Prepare for deprecation of security manager (JEP-411)  (was: Prepare for deprecation of security manager checkPermission (JEP-411))

> Prepare for deprecation of security manager (JEP-411)
> -----------------------------------------------------
>
>                 Key: GROOVY-10581
>                 URL: https://issues.apache.org/jira/browse/GROOVY-10581
>             Project: Groovy
>          Issue Type: Task
>            Reporter: Paul King
>            Assignee: Paul King
>            Priority: Major
>             Fix For: 4.0.0-rc-2
>
>
> JEP-411 indicates that the security manager will be deprecated and removed in a future JDK. Groovy currently optionally allows use of a security manager. We should as a first step, refactor calls, e.g. to AccessController.doPrivileged to funnel through the one spot as part of the VMPlugin mechanism. We can then still allow such calls on JDKs that support it and remove when needed when no longer supported.



--
This message was sent by Atlassian Jira
(v8.20.1#820001)