[
https://issues.apache.org/jira/browse/GROOVY-10479?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Paul King updated GROOVY-10479:
-------------------------------
Description: Due to [JEP-411|https://openjdk.java.net/jeps/411], the
security manager is being slowly phased out. This results in warnings on JDK17
and runtime exceptions on JDK18. Groovy is already making progress on how to
handle that change in other areas. This issue is specifically to disable Ant
tests on JDK18 until such time as Ant itself no longer has the issue as per
[Ant bugzilla issue
65381|https://bz.apache.org/bugzilla/show_bug.cgi?id=65381]. If Ant fixes or
implements its own workaround mechanism our goal would be to re-enable the
tests affected by this issue. (was: Due to
[JEP-411|https://openjdk.java.net/jeps/411], the security manager is being
slowly phased out. This results in warnings on JDK17 and runtime exceptions on
JDK18. Groovy is already making progress on how to handle that change in other
areas. This issue is specifically to disable Ant tests on JDK18 until such time
as Ant itself no longer has the issue as per [Ant bugzilla issue
65381|https://bz.apache.org/bugzilla/show_bug.cgi?id=65381]. If Ant fixes or
implements a mechanism our goal would be to re-enable the tests affected by
this issue.)
> Disable Ant tests which don't fork under JDK18
> ----------------------------------------------
>
> Key: GROOVY-10479
> URL: https://issues.apache.org/jira/browse/GROOVY-10479
> Project: Groovy
> Issue Type: Task
> Reporter: Paul King
> Priority: Major
>
> Due to [JEP-411|https://openjdk.java.net/jeps/411], the security manager is
> being slowly phased out. This results in warnings on JDK17 and runtime
> exceptions on JDK18. Groovy is already making progress on how to handle that
> change in other areas. This issue is specifically to disable Ant tests on
> JDK18 until such time as Ant itself no longer has the issue as per [Ant
> bugzilla issue 65381|https://bz.apache.org/bugzilla/show_bug.cgi?id=65381].
> If Ant fixes or implements its own workaround mechanism our goal would be to
> re-enable the tests affected by this issue.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
