This is an automated email from the ASF dual-hosted git repository.

jaikiran pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/ant.git


The following commit(s) were added to refs/heads/master by this push:
     new a4de9db7a update WHATSNEW to explain the SecurityManager changes
a4de9db7a is described below

commit a4de9db7a01ca44d0b171c972a997bf22545676e
Author: Jaikiran Pai <[email protected]>
AuthorDate: Thu Aug 10 22:30:19 2023 +0530

    update WHATSNEW to explain the SecurityManager changes
---
 WHATSNEW | 12 ++++++++++++
 1 file changed, 12 insertions(+)

diff --git a/WHATSNEW b/WHATSNEW
index 426e855f2..61c7fb917 100644
--- a/WHATSNEW
+++ b/WHATSNEW
@@ -8,6 +8,18 @@ Changes that could break older environments:
    later may be costly (for example in the case of a StringResource).
    Bugzilla Report 66496
 
+ * When using Java 18 or higher, Ant will no longer use Java SecurityManager
+   because it has been deprecated for removal and by default is disallowed
+   to be set at runtime https://openjdk.org/jeps/411.
+   This will mean that the "<permissions>" type is no longer functional when
+   using Java 18 or higher.
+   Furthermore, when using Java 18 or higher, if the build executes
+   tasks that call "java.lang.System.exit()" and if those tasks aren't
+   running in a forked VM of their own, then such tasks will now kill
+   the entire Ant build process. It is recommended that such tasks be
+   updated to launch in a forked JVM so that the System.exit() call
+   will not impact the JVM in which Ant process runs.
+
 Fixed bugs:
 -----------
 

Reply via email to