You are viewing a plain text version of this content. The canonical link for it is here.
Posted to user@ant.apache.org by Jaikiran Pai <ja...@apache.org> on 2023/08/16 12:35:22 UTC
[VOTE] Release Apache Ant 1.10.14 based on RC1
Hello everyone,
I've created RC1 release candidate for Ant 1.10.14 release:
git tag: ANT_1.10.14_RC1
on commit: 53f19eccf49acf526415997046dca5a5135b0e8f
tarballs: https://dist.apache.org/repos/dist/dev/ant/
revision: 63474
Maven artifacts:
https://repository.apache.org/content/repositories/orgapacheant-1057
Apart from regular bug fixes, this 1.10.14 release has crucial changes
around Ant's usage of Java SecurityManager. Many of you will be aware
that Java 17 deprecated (for removal) the use of SecurityManager. Java
18 then disallowed setting SecurityManager at runtime, by default. Ant
internally sets a SecurityManager at runtime to prevent System.exit()
calls from within tasks, from killing the JVM in which Ant process is
running. In Ant 1.10.13, we tried to keep using the SecurityManager
internally for a few more releases in Ant, to facilitate projects to use
Ant without requiring (major) changes to their build. The workarounds we
put in place in Ant 1.10.13 were brittle and complex and although we had
hoped they won't break user builds, they did end up breaking several
builds. Ultimately, these workarounds for usage of SecurityManager are
no longer feasible or adding value.
As such, this 1.10.14 release of Ant will no longer use (or set) Java
SecurityManager when running on Java versions 18 and higher. This has
implications for projects using Ant. Specifically, if any of the build
tasks (for example the "<java>", "<junit>" or "<junitlauncher>" tasks)
or libraries used in those tasks are calling System.exit() or
Runtime.exit() and aren't forking a new JVM, then when running on Java
18 and higher, they may notice that the Ant JVM process gets killed.
Such builds are recommended to either not call
System.exit()/Runtime.exit() or use the "fork=true" option in relevant
tasks (wherever appropriate).
Furthermore, the usage of "<permissions>" type when running on Java 18
and higher is no longer supported. More details are available in the
manual of that type https://dist.apache.org/repos/dist/dev/ant/manual/.
The complete set of changes in this release are noted in
https://dist.apache.org/repos/dist/dev/ant/RELEASE-NOTES-1.10.14.html.
Please do give this proposed release version a try against whichever
Java runtime versions you plan to use it against (this version requires
a minimum of Java 8 runtime, like any other Ant 1.10.x versions). Even
if you don't vote, if you do run into issues, please report back - it
takes time to create Ant releases, so catching any blocker issues (like
some of which we saw after Ant 1.10.13 was released) early will help fix
them sooner.
This vote will be open for at least 72 hours and close no earlier than
19th August 2023 12 PM.
-Jaikiran
---------------------------------------------------------------------
To unsubscribe, e-mail: user-unsubscribe@ant.apache.org
For additional commands, e-mail: user-help@ant.apache.org
Re: [VOTE] Release Apache Ant 1.10.14 based on RC1
Posted by Jaikiran Pai <ja...@apache.org>.
+1
- Downloaded the newer version and checked the NOTICE file
- verified the checksum
- Built some projects using this newer version, on Java 8, 17 and 20
- Checked manual docs for some of the tasks
-Jaikiran
On 16/08/23 6:05 pm, Jaikiran Pai wrote:
> Hello everyone,
>
> I've created RC1 release candidate for Ant 1.10.14 release:
>
> git tag: ANT_1.10.14_RC1
>
> on commit: 53f19eccf49acf526415997046dca5a5135b0e8f
>
> tarballs: https://dist.apache.org/repos/dist/dev/ant/
>
> revision: 63474
>
> Maven artifacts:
> https://repository.apache.org/content/repositories/orgapacheant-1057
>
>
> Apart from regular bug fixes, this 1.10.14 release has crucial changes
> around Ant's usage of Java SecurityManager. Many of you will be aware
> that Java 17 deprecated (for removal) the use of SecurityManager. Java
> 18 then disallowed setting SecurityManager at runtime, by default. Ant
> internally sets a SecurityManager at runtime to prevent System.exit()
> calls from within tasks, from killing the JVM in which Ant process is
> running. In Ant 1.10.13, we tried to keep using the SecurityManager
> internally for a few more releases in Ant, to facilitate projects to
> use Ant without requiring (major) changes to their build. The
> workarounds we put in place in Ant 1.10.13 were brittle and complex
> and although we had hoped they won't break user builds, they did end
> up breaking several builds. Ultimately, these workarounds for usage of
> SecurityManager are no longer feasible or adding value.
>
> As such, this 1.10.14 release of Ant will no longer use (or set) Java
> SecurityManager when running on Java versions 18 and higher. This has
> implications for projects using Ant. Specifically, if any of the build
> tasks (for example the "<java>", "<junit>" or "<junitlauncher>" tasks)
> or libraries used in those tasks are calling System.exit() or
> Runtime.exit() and aren't forking a new JVM, then when running on Java
> 18 and higher, they may notice that the Ant JVM process gets killed.
> Such builds are recommended to either not call
> System.exit()/Runtime.exit() or use the "fork=true" option in relevant
> tasks (wherever appropriate).
>
> Furthermore, the usage of "<permissions>" type when running on Java 18
> and higher is no longer supported. More details are available in the
> manual of that type https://dist.apache.org/repos/dist/dev/ant/manual/.
>
> The complete set of changes in this release are noted in
> https://dist.apache.org/repos/dist/dev/ant/RELEASE-NOTES-1.10.14.html.
>
> Please do give this proposed release version a try against whichever
> Java runtime versions you plan to use it against (this version
> requires a minimum of Java 8 runtime, like any other Ant 1.10.x
> versions). Even if you don't vote, if you do run into issues, please
> report back - it takes time to create Ant releases, so catching any
> blocker issues (like some of which we saw after Ant 1.10.13 was
> released) early will help fix them sooner.
>
> This vote will be open for at least 72 hours and close no earlier than
> 19th August 2023 12 PM.
>
> -Jaikiran
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@ant.apache.org
For additional commands, e-mail: dev-help@ant.apache.org
Re: [VOTE] Release Apache Ant 1.10.14 based on RC1
Posted by Gary Gregory <gg...@rocketsoftware.com>.
Sounds good!
Thank you,
Gary
________________________________
From: Jaikiran Pai <ja...@apache.org>
Sent: Wednesday, August 16, 2023 8:57:09 PM
To: Ant Developers List <de...@ant.apache.org>; Gary Gregory <gg...@rocketsoftware.com>; Ant Users List <us...@ant.apache.org>
Subject: Re: [VOTE] Release Apache Ant 1.10.14 based on RC1
EXTERNAL EMAIL
Hello Gary,
Yes, that allow.class which was introduced in 1.10.13 is no longer part
of Ant 1.10.14. I think, as you note, adding it to the release notes
sounds like the right thing, since a couple of projects had specifically
run into issue with that class. I'll update the release note after the
voting completes (won't create a new RC for that).
-Jaikiran
On 16/08/23 6:42 pm, Gary Gregory wrote:
> (AFK) Does this remove the class file in the root of the ant-launcher jar which caused JPMS issues? If so, it might be worth mentioning in the release noyes.
>
> Gary
>
> ________________________________
> From: Jaikiran Pai <ja...@apache.org>
> Sent: Wednesday, August 16, 2023 8:35:22 AM
> To: user@ant.apache.org <us...@ant.apache.org>; dev@ant.apache.org <de...@ant.apache.org>
> Subject: [VOTE] Release Apache Ant 1.10.14 based on RC1
>
> EXTERNAL EMAIL
>
>
>
>
> Hello everyone,
>
> I've created RC1 release candidate for Ant 1.10.14 release:
>
> git tag: ANT_1.10.14_RC1
>
> on commit: 53f19eccf49acf526415997046dca5a5135b0e8f
>
> tarballs: https://dist.apache.org/repos/dist/dev/ant/<https://dist.apache.org/repos/dist/dev/ant><https://dist.apache.org/repos/dist/dev/ant<https://dist.apache.org/repos/dist/dev/ant>>
>
> revision: 63474
>
> Maven artifacts:
> https://repository.apache.org/content/repositories/orgapacheant-1057<https://repository.apache.org/content/repositories/orgapacheant-1057><https://repository.apache.org/content/repositories/orgapacheant-1057<https://repository.apache.org/content/repositories/orgapacheant-1057>>
>
>
> Apart from regular bug fixes, this 1.10.14 release has crucial changes
> around Ant's usage of Java SecurityManager. Many of you will be aware
> that Java 17 deprecated (for removal) the use of SecurityManager. Java
> 18 then disallowed setting SecurityManager at runtime, by default. Ant
> internally sets a SecurityManager at runtime to prevent System.exit()
> calls from within tasks, from killing the JVM in which Ant process is
> running. In Ant 1.10.13, we tried to keep using the SecurityManager
> internally for a few more releases in Ant, to facilitate projects to use
> Ant without requiring (major) changes to their build. The workarounds we
> put in place in Ant 1.10.13 were brittle and complex and although we had
> hoped they won't break user builds, they did end up breaking several
> builds. Ultimately, these workarounds for usage of SecurityManager are
> no longer feasible or adding value.
>
> As such, this 1.10.14 release of Ant will no longer use (or set) Java
> SecurityManager when running on Java versions 18 and higher. This has
> implications for projects using Ant. Specifically, if any of the build
> tasks (for example the "<java>", "<junit>" or "<junitlauncher>" tasks)
> or libraries used in those tasks are calling System.exit() or
> Runtime.exit() and aren't forking a new JVM, then when running on Java
> 18 and higher, they may notice that the Ant JVM process gets killed.
> Such builds are recommended to either not call
> System.exit()/Runtime.exit() or use the "fork=true" option in relevant
> tasks (wherever appropriate).
>
> Furthermore, the usage of "<permissions>" type when running on Java 18
> and higher is no longer supported. More details are available in the
> manual of that type https://dist.apache.org/repos/dist/dev/ant/manual/<https://dist.apache.org/repos/dist/dev/ant/manual><https://dist.apache.org/repos/dist/dev/ant/manual<https://dist.apache.org/repos/dist/dev/ant/manual>>.
>
> The complete set of changes in this release are noted in
> https://dist.apache.org/repos/dist/dev/ant/RELEASE-NOTES-1.10.14.html<https://dist.apache.org/repos/dist/dev/ant/RELEASE-NOTES-1.10.14.html><https://dist.apache.org/repos/dist/dev/ant/RELEASE-NOTES-1.10.14.html<https://dist.apache.org/repos/dist/dev/ant/RELEASE-NOTES-1.10.14.html>>.
>
> Please do give this proposed release version a try against whichever
> Java runtime versions you plan to use it against (this version requires
> a minimum of Java 8 runtime, like any other Ant 1.10.x versions). Even
> if you don't vote, if you do run into issues, please report back - it
> takes time to create Ant releases, so catching any blocker issues (like
> some of which we saw after Ant 1.10.13 was released) early will help fix
> them sooner.
>
> This vote will be open for at least 72 hours and close no earlier than
> 19th August 2023 12 PM.
>
> -Jaikiran
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: user-unsubscribe@ant.apache.org
> For additional commands, e-mail: user-help@ant.apache.org
>
> ================================
> Rocket Software, Inc. and subsidiaries ? 77 Fourth Avenue, Waltham MA 02451 ? Main Office Toll Free Number: +1 855.577.4323
> Contact Customer Support: https://my.rocketsoftware.com/RocketCommunity/RCEmailSupport<https://my.rocketsoftware.com/RocketCommunity/RCEmailSupport>
> Unsubscribe from Marketing Messages/Manage Your Subscription Preferences - http://www.rocketsoftware.com/manage-your-email-preferences<http://www.rocketsoftware.com/manage-your-email-preferences>
> Privacy Policy - http://www.rocketsoftware.com/company/legal/privacy-policy<http://www.rocketsoftware.com/company/legal/privacy-policy>
> ================================
>
> This communication and any attachments may contain confidential information of Rocket Software, Inc. All unauthorized use, disclosure or distribution is prohibited. If you are not the intended recipient, please notify Rocket Software immediately and destroy all copies of this communication. Thank you.
>
Re: [VOTE] Release Apache Ant 1.10.14 based on RC1
Posted by Gary Gregory <gg...@rocketsoftware.com>.
Sounds good!
Thank you,
Gary
________________________________
From: Jaikiran Pai <ja...@apache.org>
Sent: Wednesday, August 16, 2023 8:57:09 PM
To: Ant Developers List <de...@ant.apache.org>; Gary Gregory <gg...@rocketsoftware.com>; Ant Users List <us...@ant.apache.org>
Subject: Re: [VOTE] Release Apache Ant 1.10.14 based on RC1
EXTERNAL EMAIL
Hello Gary,
Yes, that allow.class which was introduced in 1.10.13 is no longer part
of Ant 1.10.14. I think, as you note, adding it to the release notes
sounds like the right thing, since a couple of projects had specifically
run into issue with that class. I'll update the release note after the
voting completes (won't create a new RC for that).
-Jaikiran
On 16/08/23 6:42 pm, Gary Gregory wrote:
> (AFK) Does this remove the class file in the root of the ant-launcher jar which caused JPMS issues? If so, it might be worth mentioning in the release noyes.
>
> Gary
>
> ________________________________
> From: Jaikiran Pai <ja...@apache.org>
> Sent: Wednesday, August 16, 2023 8:35:22 AM
> To: user@ant.apache.org <us...@ant.apache.org>; dev@ant.apache.org <de...@ant.apache.org>
> Subject: [VOTE] Release Apache Ant 1.10.14 based on RC1
>
> EXTERNAL EMAIL
>
>
>
>
> Hello everyone,
>
> I've created RC1 release candidate for Ant 1.10.14 release:
>
> git tag: ANT_1.10.14_RC1
>
> on commit: 53f19eccf49acf526415997046dca5a5135b0e8f
>
> tarballs: https://dist.apache.org/repos/dist/dev/ant/<https://dist.apache.org/repos/dist/dev/ant><https://dist.apache.org/repos/dist/dev/ant<https://dist.apache.org/repos/dist/dev/ant>>
>
> revision: 63474
>
> Maven artifacts:
> https://repository.apache.org/content/repositories/orgapacheant-1057<https://repository.apache.org/content/repositories/orgapacheant-1057><https://repository.apache.org/content/repositories/orgapacheant-1057<https://repository.apache.org/content/repositories/orgapacheant-1057>>
>
>
> Apart from regular bug fixes, this 1.10.14 release has crucial changes
> around Ant's usage of Java SecurityManager. Many of you will be aware
> that Java 17 deprecated (for removal) the use of SecurityManager. Java
> 18 then disallowed setting SecurityManager at runtime, by default. Ant
> internally sets a SecurityManager at runtime to prevent System.exit()
> calls from within tasks, from killing the JVM in which Ant process is
> running. In Ant 1.10.13, we tried to keep using the SecurityManager
> internally for a few more releases in Ant, to facilitate projects to use
> Ant without requiring (major) changes to their build. The workarounds we
> put in place in Ant 1.10.13 were brittle and complex and although we had
> hoped they won't break user builds, they did end up breaking several
> builds. Ultimately, these workarounds for usage of SecurityManager are
> no longer feasible or adding value.
>
> As such, this 1.10.14 release of Ant will no longer use (or set) Java
> SecurityManager when running on Java versions 18 and higher. This has
> implications for projects using Ant. Specifically, if any of the build
> tasks (for example the "<java>", "<junit>" or "<junitlauncher>" tasks)
> or libraries used in those tasks are calling System.exit() or
> Runtime.exit() and aren't forking a new JVM, then when running on Java
> 18 and higher, they may notice that the Ant JVM process gets killed.
> Such builds are recommended to either not call
> System.exit()/Runtime.exit() or use the "fork=true" option in relevant
> tasks (wherever appropriate).
>
> Furthermore, the usage of "<permissions>" type when running on Java 18
> and higher is no longer supported. More details are available in the
> manual of that type https://dist.apache.org/repos/dist/dev/ant/manual/<https://dist.apache.org/repos/dist/dev/ant/manual><https://dist.apache.org/repos/dist/dev/ant/manual<https://dist.apache.org/repos/dist/dev/ant/manual>>.
>
> The complete set of changes in this release are noted in
> https://dist.apache.org/repos/dist/dev/ant/RELEASE-NOTES-1.10.14.html<https://dist.apache.org/repos/dist/dev/ant/RELEASE-NOTES-1.10.14.html><https://dist.apache.org/repos/dist/dev/ant/RELEASE-NOTES-1.10.14.html<https://dist.apache.org/repos/dist/dev/ant/RELEASE-NOTES-1.10.14.html>>.
>
> Please do give this proposed release version a try against whichever
> Java runtime versions you plan to use it against (this version requires
> a minimum of Java 8 runtime, like any other Ant 1.10.x versions). Even
> if you don't vote, if you do run into issues, please report back - it
> takes time to create Ant releases, so catching any blocker issues (like
> some of which we saw after Ant 1.10.13 was released) early will help fix
> them sooner.
>
> This vote will be open for at least 72 hours and close no earlier than
> 19th August 2023 12 PM.
>
> -Jaikiran
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: user-unsubscribe@ant.apache.org
> For additional commands, e-mail: user-help@ant.apache.org
>
> ================================
> Rocket Software, Inc. and subsidiaries ? 77 Fourth Avenue, Waltham MA 02451 ? Main Office Toll Free Number: +1 855.577.4323
> Contact Customer Support: https://my.rocketsoftware.com/RocketCommunity/RCEmailSupport<https://my.rocketsoftware.com/RocketCommunity/RCEmailSupport>
> Unsubscribe from Marketing Messages/Manage Your Subscription Preferences - http://www.rocketsoftware.com/manage-your-email-preferences<http://www.rocketsoftware.com/manage-your-email-preferences>
> Privacy Policy - http://www.rocketsoftware.com/company/legal/privacy-policy<http://www.rocketsoftware.com/company/legal/privacy-policy>
> ================================
>
> This communication and any attachments may contain confidential information of Rocket Software, Inc. All unauthorized use, disclosure or distribution is prohibited. If you are not the intended recipient, please notify Rocket Software immediately and destroy all copies of this communication. Thank you.
>
Re: [VOTE] Release Apache Ant 1.10.14 based on RC1
Posted by Jaikiran Pai <ja...@apache.org>.
Hello Gary,
Yes, that allow.class which was introduced in 1.10.13 is no longer part
of Ant 1.10.14. I think, as you note, adding it to the release notes
sounds like the right thing, since a couple of projects had specifically
run into issue with that class. I'll update the release note after the
voting completes (won't create a new RC for that).
-Jaikiran
On 16/08/23 6:42 pm, Gary Gregory wrote:
> (AFK) Does this remove the class file in the root of the ant-launcher jar which caused JPMS issues? If so, it might be worth mentioning in the release noyes.
>
> Gary
>
> ________________________________
> From: Jaikiran Pai <ja...@apache.org>
> Sent: Wednesday, August 16, 2023 8:35:22 AM
> To: user@ant.apache.org <us...@ant.apache.org>; dev@ant.apache.org <de...@ant.apache.org>
> Subject: [VOTE] Release Apache Ant 1.10.14 based on RC1
>
> EXTERNAL EMAIL
>
>
>
>
> Hello everyone,
>
> I've created RC1 release candidate for Ant 1.10.14 release:
>
> git tag: ANT_1.10.14_RC1
>
> on commit: 53f19eccf49acf526415997046dca5a5135b0e8f
>
> tarballs: https://dist.apache.org/repos/dist/dev/ant/<https://dist.apache.org/repos/dist/dev/ant>
>
> revision: 63474
>
> Maven artifacts:
> https://repository.apache.org/content/repositories/orgapacheant-1057<https://repository.apache.org/content/repositories/orgapacheant-1057>
>
>
> Apart from regular bug fixes, this 1.10.14 release has crucial changes
> around Ant's usage of Java SecurityManager. Many of you will be aware
> that Java 17 deprecated (for removal) the use of SecurityManager. Java
> 18 then disallowed setting SecurityManager at runtime, by default. Ant
> internally sets a SecurityManager at runtime to prevent System.exit()
> calls from within tasks, from killing the JVM in which Ant process is
> running. In Ant 1.10.13, we tried to keep using the SecurityManager
> internally for a few more releases in Ant, to facilitate projects to use
> Ant without requiring (major) changes to their build. The workarounds we
> put in place in Ant 1.10.13 were brittle and complex and although we had
> hoped they won't break user builds, they did end up breaking several
> builds. Ultimately, these workarounds for usage of SecurityManager are
> no longer feasible or adding value.
>
> As such, this 1.10.14 release of Ant will no longer use (or set) Java
> SecurityManager when running on Java versions 18 and higher. This has
> implications for projects using Ant. Specifically, if any of the build
> tasks (for example the "<java>", "<junit>" or "<junitlauncher>" tasks)
> or libraries used in those tasks are calling System.exit() or
> Runtime.exit() and aren't forking a new JVM, then when running on Java
> 18 and higher, they may notice that the Ant JVM process gets killed.
> Such builds are recommended to either not call
> System.exit()/Runtime.exit() or use the "fork=true" option in relevant
> tasks (wherever appropriate).
>
> Furthermore, the usage of "<permissions>" type when running on Java 18
> and higher is no longer supported. More details are available in the
> manual of that type https://dist.apache.org/repos/dist/dev/ant/manual/<https://dist.apache.org/repos/dist/dev/ant/manual>.
>
> The complete set of changes in this release are noted in
> https://dist.apache.org/repos/dist/dev/ant/RELEASE-NOTES-1.10.14.html<https://dist.apache.org/repos/dist/dev/ant/RELEASE-NOTES-1.10.14.html>.
>
> Please do give this proposed release version a try against whichever
> Java runtime versions you plan to use it against (this version requires
> a minimum of Java 8 runtime, like any other Ant 1.10.x versions). Even
> if you don't vote, if you do run into issues, please report back - it
> takes time to create Ant releases, so catching any blocker issues (like
> some of which we saw after Ant 1.10.13 was released) early will help fix
> them sooner.
>
> This vote will be open for at least 72 hours and close no earlier than
> 19th August 2023 12 PM.
>
> -Jaikiran
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: user-unsubscribe@ant.apache.org
> For additional commands, e-mail: user-help@ant.apache.org
>
> ================================
> Rocket Software, Inc. and subsidiaries ? 77 Fourth Avenue, Waltham MA 02451 ? Main Office Toll Free Number: +1 855.577.4323
> Contact Customer Support: https://my.rocketsoftware.com/RocketCommunity/RCEmailSupport
> Unsubscribe from Marketing Messages/Manage Your Subscription Preferences - http://www.rocketsoftware.com/manage-your-email-preferences
> Privacy Policy - http://www.rocketsoftware.com/company/legal/privacy-policy
> ================================
>
> This communication and any attachments may contain confidential information of Rocket Software, Inc. All unauthorized use, disclosure or distribution is prohibited. If you are not the intended recipient, please notify Rocket Software immediately and destroy all copies of this communication. Thank you.
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@ant.apache.org
For additional commands, e-mail: dev-help@ant.apache.org
Re: [VOTE] Release Apache Ant 1.10.14 based on RC1
Posted by Jaikiran Pai <ja...@apache.org>.
Hello Gary,
Yes, that allow.class which was introduced in 1.10.13 is no longer part
of Ant 1.10.14. I think, as you note, adding it to the release notes
sounds like the right thing, since a couple of projects had specifically
run into issue with that class. I'll update the release note after the
voting completes (won't create a new RC for that).
-Jaikiran
On 16/08/23 6:42 pm, Gary Gregory wrote:
> (AFK) Does this remove the class file in the root of the ant-launcher jar which caused JPMS issues? If so, it might be worth mentioning in the release noyes.
>
> Gary
>
> ________________________________
> From: Jaikiran Pai <ja...@apache.org>
> Sent: Wednesday, August 16, 2023 8:35:22 AM
> To: user@ant.apache.org <us...@ant.apache.org>; dev@ant.apache.org <de...@ant.apache.org>
> Subject: [VOTE] Release Apache Ant 1.10.14 based on RC1
>
> EXTERNAL EMAIL
>
>
>
>
> Hello everyone,
>
> I've created RC1 release candidate for Ant 1.10.14 release:
>
> git tag: ANT_1.10.14_RC1
>
> on commit: 53f19eccf49acf526415997046dca5a5135b0e8f
>
> tarballs: https://dist.apache.org/repos/dist/dev/ant/<https://dist.apache.org/repos/dist/dev/ant>
>
> revision: 63474
>
> Maven artifacts:
> https://repository.apache.org/content/repositories/orgapacheant-1057<https://repository.apache.org/content/repositories/orgapacheant-1057>
>
>
> Apart from regular bug fixes, this 1.10.14 release has crucial changes
> around Ant's usage of Java SecurityManager. Many of you will be aware
> that Java 17 deprecated (for removal) the use of SecurityManager. Java
> 18 then disallowed setting SecurityManager at runtime, by default. Ant
> internally sets a SecurityManager at runtime to prevent System.exit()
> calls from within tasks, from killing the JVM in which Ant process is
> running. In Ant 1.10.13, we tried to keep using the SecurityManager
> internally for a few more releases in Ant, to facilitate projects to use
> Ant without requiring (major) changes to their build. The workarounds we
> put in place in Ant 1.10.13 were brittle and complex and although we had
> hoped they won't break user builds, they did end up breaking several
> builds. Ultimately, these workarounds for usage of SecurityManager are
> no longer feasible or adding value.
>
> As such, this 1.10.14 release of Ant will no longer use (or set) Java
> SecurityManager when running on Java versions 18 and higher. This has
> implications for projects using Ant. Specifically, if any of the build
> tasks (for example the "<java>", "<junit>" or "<junitlauncher>" tasks)
> or libraries used in those tasks are calling System.exit() or
> Runtime.exit() and aren't forking a new JVM, then when running on Java
> 18 and higher, they may notice that the Ant JVM process gets killed.
> Such builds are recommended to either not call
> System.exit()/Runtime.exit() or use the "fork=true" option in relevant
> tasks (wherever appropriate).
>
> Furthermore, the usage of "<permissions>" type when running on Java 18
> and higher is no longer supported. More details are available in the
> manual of that type https://dist.apache.org/repos/dist/dev/ant/manual/<https://dist.apache.org/repos/dist/dev/ant/manual>.
>
> The complete set of changes in this release are noted in
> https://dist.apache.org/repos/dist/dev/ant/RELEASE-NOTES-1.10.14.html<https://dist.apache.org/repos/dist/dev/ant/RELEASE-NOTES-1.10.14.html>.
>
> Please do give this proposed release version a try against whichever
> Java runtime versions you plan to use it against (this version requires
> a minimum of Java 8 runtime, like any other Ant 1.10.x versions). Even
> if you don't vote, if you do run into issues, please report back - it
> takes time to create Ant releases, so catching any blocker issues (like
> some of which we saw after Ant 1.10.13 was released) early will help fix
> them sooner.
>
> This vote will be open for at least 72 hours and close no earlier than
> 19th August 2023 12 PM.
>
> -Jaikiran
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: user-unsubscribe@ant.apache.org
> For additional commands, e-mail: user-help@ant.apache.org
>
> ================================
> Rocket Software, Inc. and subsidiaries ? 77 Fourth Avenue, Waltham MA 02451 ? Main Office Toll Free Number: +1 855.577.4323
> Contact Customer Support: https://my.rocketsoftware.com/RocketCommunity/RCEmailSupport
> Unsubscribe from Marketing Messages/Manage Your Subscription Preferences - http://www.rocketsoftware.com/manage-your-email-preferences
> Privacy Policy - http://www.rocketsoftware.com/company/legal/privacy-policy
> ================================
>
> This communication and any attachments may contain confidential information of Rocket Software, Inc. All unauthorized use, disclosure or distribution is prohibited. If you are not the intended recipient, please notify Rocket Software immediately and destroy all copies of this communication. Thank you.
>
---------------------------------------------------------------------
To unsubscribe, e-mail: user-unsubscribe@ant.apache.org
For additional commands, e-mail: user-help@ant.apache.org
Re: [VOTE] Release Apache Ant 1.10.14 based on RC1
Posted by Gary Gregory <gg...@rocketsoftware.com>.
(AFK) Does this remove the class file in the root of the ant-launcher jar which caused JPMS issues? If so, it might be worth mentioning in the release noyes.
Gary
________________________________
From: Jaikiran Pai <ja...@apache.org>
Sent: Wednesday, August 16, 2023 8:35:22 AM
To: user@ant.apache.org <us...@ant.apache.org>; dev@ant.apache.org <de...@ant.apache.org>
Subject: [VOTE] Release Apache Ant 1.10.14 based on RC1
EXTERNAL EMAIL
Hello everyone,
I've created RC1 release candidate for Ant 1.10.14 release:
git tag: ANT_1.10.14_RC1
on commit: 53f19eccf49acf526415997046dca5a5135b0e8f
tarballs: https://dist.apache.org/repos/dist/dev/ant/<https://dist.apache.org/repos/dist/dev/ant>
revision: 63474
Maven artifacts:
https://repository.apache.org/content/repositories/orgapacheant-1057<https://repository.apache.org/content/repositories/orgapacheant-1057>
Apart from regular bug fixes, this 1.10.14 release has crucial changes
around Ant's usage of Java SecurityManager. Many of you will be aware
that Java 17 deprecated (for removal) the use of SecurityManager. Java
18 then disallowed setting SecurityManager at runtime, by default. Ant
internally sets a SecurityManager at runtime to prevent System.exit()
calls from within tasks, from killing the JVM in which Ant process is
running. In Ant 1.10.13, we tried to keep using the SecurityManager
internally for a few more releases in Ant, to facilitate projects to use
Ant without requiring (major) changes to their build. The workarounds we
put in place in Ant 1.10.13 were brittle and complex and although we had
hoped they won't break user builds, they did end up breaking several
builds. Ultimately, these workarounds for usage of SecurityManager are
no longer feasible or adding value.
As such, this 1.10.14 release of Ant will no longer use (or set) Java
SecurityManager when running on Java versions 18 and higher. This has
implications for projects using Ant. Specifically, if any of the build
tasks (for example the "<java>", "<junit>" or "<junitlauncher>" tasks)
or libraries used in those tasks are calling System.exit() or
Runtime.exit() and aren't forking a new JVM, then when running on Java
18 and higher, they may notice that the Ant JVM process gets killed.
Such builds are recommended to either not call
System.exit()/Runtime.exit() or use the "fork=true" option in relevant
tasks (wherever appropriate).
Furthermore, the usage of "<permissions>" type when running on Java 18
and higher is no longer supported. More details are available in the
manual of that type https://dist.apache.org/repos/dist/dev/ant/manual/<https://dist.apache.org/repos/dist/dev/ant/manual>.
The complete set of changes in this release are noted in
https://dist.apache.org/repos/dist/dev/ant/RELEASE-NOTES-1.10.14.html<https://dist.apache.org/repos/dist/dev/ant/RELEASE-NOTES-1.10.14.html>.
Please do give this proposed release version a try against whichever
Java runtime versions you plan to use it against (this version requires
a minimum of Java 8 runtime, like any other Ant 1.10.x versions). Even
if you don't vote, if you do run into issues, please report back - it
takes time to create Ant releases, so catching any blocker issues (like
some of which we saw after Ant 1.10.13 was released) early will help fix
them sooner.
This vote will be open for at least 72 hours and close no earlier than
19th August 2023 12 PM.
-Jaikiran
---------------------------------------------------------------------
To unsubscribe, e-mail: user-unsubscribe@ant.apache.org
For additional commands, e-mail: user-help@ant.apache.org
================================
Rocket Software, Inc. and subsidiaries ? 77 Fourth Avenue, Waltham MA 02451 ? Main Office Toll Free Number: +1 855.577.4323
Contact Customer Support: https://my.rocketsoftware.com/RocketCommunity/RCEmailSupport
Unsubscribe from Marketing Messages/Manage Your Subscription Preferences - http://www.rocketsoftware.com/manage-your-email-preferences
Privacy Policy - http://www.rocketsoftware.com/company/legal/privacy-policy
================================
This communication and any attachments may contain confidential information of Rocket Software, Inc. All unauthorized use, disclosure or distribution is prohibited. If you are not the intended recipient, please notify Rocket Software immediately and destroy all copies of this communication. Thank you.
Re: [VOTE] Release Apache Ant 1.10.14 based on RC1
Posted by Maarten Coene <ma...@yahoo.com.INVALID>.
Thanks Jaikiran!
Here is my vote: +1
Maarten
Op woensdag 16 augustus 2023 om 14:35:43 CEST schreef Jaikiran Pai <ja...@apache.org>:
Hello everyone,
I've created RC1 release candidate for Ant 1.10.14 release:
git tag: ANT_1.10.14_RC1
on commit: 53f19eccf49acf526415997046dca5a5135b0e8f
tarballs: https://dist.apache.org/repos/dist/dev/ant/
revision: 63474
Maven artifacts:
https://repository.apache.org/content/repositories/orgapacheant-1057
Apart from regular bug fixes, this 1.10.14 release has crucial changes
around Ant's usage of Java SecurityManager. Many of you will be aware
that Java 17 deprecated (for removal) the use of SecurityManager. Java
18 then disallowed setting SecurityManager at runtime, by default. Ant
internally sets a SecurityManager at runtime to prevent System.exit()
calls from within tasks, from killing the JVM in which Ant process is
running. In Ant 1.10.13, we tried to keep using the SecurityManager
internally for a few more releases in Ant, to facilitate projects to use
Ant without requiring (major) changes to their build. The workarounds we
put in place in Ant 1.10.13 were brittle and complex and although we had
hoped they won't break user builds, they did end up breaking several
builds. Ultimately, these workarounds for usage of SecurityManager are
no longer feasible or adding value.
As such, this 1.10.14 release of Ant will no longer use (or set) Java
SecurityManager when running on Java versions 18 and higher. This has
implications for projects using Ant. Specifically, if any of the build
tasks (for example the "<java>", "<junit>" or "<junitlauncher>" tasks)
or libraries used in those tasks are calling System.exit() or
Runtime.exit() and aren't forking a new JVM, then when running on Java
18 and higher, they may notice that the Ant JVM process gets killed.
Such builds are recommended to either not call
System.exit()/Runtime.exit() or use the "fork=true" option in relevant
tasks (wherever appropriate).
Furthermore, the usage of "<permissions>" type when running on Java 18
and higher is no longer supported. More details are available in the
manual of that type https://dist.apache.org/repos/dist/dev/ant/manual/.
The complete set of changes in this release are noted in
https://dist.apache.org/repos/dist/dev/ant/RELEASE-NOTES-1.10.14.html.
Please do give this proposed release version a try against whichever
Java runtime versions you plan to use it against (this version requires
a minimum of Java 8 runtime, like any other Ant 1.10.x versions). Even
if you don't vote, if you do run into issues, please report back - it
takes time to create Ant releases, so catching any blocker issues (like
some of which we saw after Ant 1.10.13 was released) early will help fix
them sooner.
This vote will be open for at least 72 hours and close no earlier than
19th August 2023 12 PM.
-Jaikiran
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@ant.apache.org
For additional commands, e-mail: dev-help@ant.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@ant.apache.org
For additional commands, e-mail: dev-help@ant.apache.org
[RESULT] Release Apache Ant 1.10.14 based on RC1
Posted by Jaikiran Pai <ja...@apache.org>.
With (binding) +1s for Stefan, Maarten, me and Paul (non-binding), this
vote has now passed. I'll now go ahead with the rest of the release process.
Thank you all for the help in moving this release forward.
-Jaikiran
On 16/08/23 6:05 pm, Jaikiran Pai wrote:
> Hello everyone,
>
> I've created RC1 release candidate for Ant 1.10.14 release:
>
> git tag: ANT_1.10.14_RC1
>
> on commit: 53f19eccf49acf526415997046dca5a5135b0e8f
>
> tarballs: https://dist.apache.org/repos/dist/dev/ant/
>
> revision: 63474
>
> Maven artifacts:
> https://repository.apache.org/content/repositories/orgapacheant-1057
>
>
> Apart from regular bug fixes, this 1.10.14 release has crucial changes
> around Ant's usage of Java SecurityManager. Many of you will be aware
> that Java 17 deprecated (for removal) the use of SecurityManager. Java
> 18 then disallowed setting SecurityManager at runtime, by default. Ant
> internally sets a SecurityManager at runtime to prevent System.exit()
> calls from within tasks, from killing the JVM in which Ant process is
> running. In Ant 1.10.13, we tried to keep using the SecurityManager
> internally for a few more releases in Ant, to facilitate projects to
> use Ant without requiring (major) changes to their build. The
> workarounds we put in place in Ant 1.10.13 were brittle and complex
> and although we had hoped they won't break user builds, they did end
> up breaking several builds. Ultimately, these workarounds for usage of
> SecurityManager are no longer feasible or adding value.
>
> As such, this 1.10.14 release of Ant will no longer use (or set) Java
> SecurityManager when running on Java versions 18 and higher. This has
> implications for projects using Ant. Specifically, if any of the build
> tasks (for example the "<java>", "<junit>" or "<junitlauncher>" tasks)
> or libraries used in those tasks are calling System.exit() or
> Runtime.exit() and aren't forking a new JVM, then when running on Java
> 18 and higher, they may notice that the Ant JVM process gets killed.
> Such builds are recommended to either not call
> System.exit()/Runtime.exit() or use the "fork=true" option in relevant
> tasks (wherever appropriate).
>
> Furthermore, the usage of "<permissions>" type when running on Java 18
> and higher is no longer supported. More details are available in the
> manual of that type https://dist.apache.org/repos/dist/dev/ant/manual/.
>
> The complete set of changes in this release are noted in
> https://dist.apache.org/repos/dist/dev/ant/RELEASE-NOTES-1.10.14.html.
>
> Please do give this proposed release version a try against whichever
> Java runtime versions you plan to use it against (this version
> requires a minimum of Java 8 runtime, like any other Ant 1.10.x
> versions). Even if you don't vote, if you do run into issues, please
> report back - it takes time to create Ant releases, so catching any
> blocker issues (like some of which we saw after Ant 1.10.13 was
> released) early will help fix them sooner.
>
> This vote will be open for at least 72 hours and close no earlier than
> 19th August 2023 12 PM.
>
> -Jaikiran
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@ant.apache.org
For additional commands, e-mail: dev-help@ant.apache.org
Re: [VOTE] Release Apache Ant 1.10.14 based on RC1
Posted by Jaikiran Pai <ja...@apache.org>.
+1
- Downloaded the newer version and checked the NOTICE file
- verified the checksum
- Built some projects using this newer version, on Java 8, 17 and 20
- Checked manual docs for some of the tasks
-Jaikiran
On 16/08/23 6:05 pm, Jaikiran Pai wrote:
> Hello everyone,
>
> I've created RC1 release candidate for Ant 1.10.14 release:
>
> git tag: ANT_1.10.14_RC1
>
> on commit: 53f19eccf49acf526415997046dca5a5135b0e8f
>
> tarballs: https://dist.apache.org/repos/dist/dev/ant/
>
> revision: 63474
>
> Maven artifacts:
> https://repository.apache.org/content/repositories/orgapacheant-1057
>
>
> Apart from regular bug fixes, this 1.10.14 release has crucial changes
> around Ant's usage of Java SecurityManager. Many of you will be aware
> that Java 17 deprecated (for removal) the use of SecurityManager. Java
> 18 then disallowed setting SecurityManager at runtime, by default. Ant
> internally sets a SecurityManager at runtime to prevent System.exit()
> calls from within tasks, from killing the JVM in which Ant process is
> running. In Ant 1.10.13, we tried to keep using the SecurityManager
> internally for a few more releases in Ant, to facilitate projects to
> use Ant without requiring (major) changes to their build. The
> workarounds we put in place in Ant 1.10.13 were brittle and complex
> and although we had hoped they won't break user builds, they did end
> up breaking several builds. Ultimately, these workarounds for usage of
> SecurityManager are no longer feasible or adding value.
>
> As such, this 1.10.14 release of Ant will no longer use (or set) Java
> SecurityManager when running on Java versions 18 and higher. This has
> implications for projects using Ant. Specifically, if any of the build
> tasks (for example the "<java>", "<junit>" or "<junitlauncher>" tasks)
> or libraries used in those tasks are calling System.exit() or
> Runtime.exit() and aren't forking a new JVM, then when running on Java
> 18 and higher, they may notice that the Ant JVM process gets killed.
> Such builds are recommended to either not call
> System.exit()/Runtime.exit() or use the "fork=true" option in relevant
> tasks (wherever appropriate).
>
> Furthermore, the usage of "<permissions>" type when running on Java 18
> and higher is no longer supported. More details are available in the
> manual of that type https://dist.apache.org/repos/dist/dev/ant/manual/.
>
> The complete set of changes in this release are noted in
> https://dist.apache.org/repos/dist/dev/ant/RELEASE-NOTES-1.10.14.html.
>
> Please do give this proposed release version a try against whichever
> Java runtime versions you plan to use it against (this version
> requires a minimum of Java 8 runtime, like any other Ant 1.10.x
> versions). Even if you don't vote, if you do run into issues, please
> report back - it takes time to create Ant releases, so catching any
> blocker issues (like some of which we saw after Ant 1.10.13 was
> released) early will help fix them sooner.
>
> This vote will be open for at least 72 hours and close no earlier than
> 19th August 2023 12 PM.
>
> -Jaikiran
>
---------------------------------------------------------------------
To unsubscribe, e-mail: user-unsubscribe@ant.apache.org
For additional commands, e-mail: user-help@ant.apache.org
Re: [VOTE] Release Apache Ant 1.10.14 based on RC1
Posted by Stefan Bodewig <bo...@apache.org>.
On 2023-08-16, Jaikiran Pai wrote:
> I've created RC1 release candidate for Ant 1.10.14 release:
+1
Stefan
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@ant.apache.org
For additional commands, e-mail: dev-help@ant.apache.org
Re: [VOTE] Release Apache Ant 1.10.14 based on RC1
Posted by Paul King <pa...@asert.com.au>.
+1 (non-binding)
I did a casual inspection of the zip artifact including checking for
LICENSE & NOTICE files, and confirming its hash & signature.
I ran the Apache Groovy test suite against the candidate maven artifacts
for JDK 17 and 19.
Cheers, Paul.
On Wed, Aug 16, 2023 at 10:35 PM Jaikiran Pai <ja...@apache.org> wrote:
> Hello everyone,
>
> I've created RC1 release candidate for Ant 1.10.14 release:
>
> git tag: ANT_1.10.14_RC1
>
> on commit: 53f19eccf49acf526415997046dca5a5135b0e8f
>
> tarballs: https://dist.apache.org/repos/dist/dev/ant/
>
> revision: 63474
>
> Maven artifacts:
> https://repository.apache.org/content/repositories/orgapacheant-1057
>
>
> Apart from regular bug fixes, this 1.10.14 release has crucial changes
> around Ant's usage of Java SecurityManager. Many of you will be aware
> that Java 17 deprecated (for removal) the use of SecurityManager. Java
> 18 then disallowed setting SecurityManager at runtime, by default. Ant
> internally sets a SecurityManager at runtime to prevent System.exit()
> calls from within tasks, from killing the JVM in which Ant process is
> running. In Ant 1.10.13, we tried to keep using the SecurityManager
> internally for a few more releases in Ant, to facilitate projects to use
> Ant without requiring (major) changes to their build. The workarounds we
> put in place in Ant 1.10.13 were brittle and complex and although we had
> hoped they won't break user builds, they did end up breaking several
> builds. Ultimately, these workarounds for usage of SecurityManager are
> no longer feasible or adding value.
>
> As such, this 1.10.14 release of Ant will no longer use (or set) Java
> SecurityManager when running on Java versions 18 and higher. This has
> implications for projects using Ant. Specifically, if any of the build
> tasks (for example the "<java>", "<junit>" or "<junitlauncher>" tasks)
> or libraries used in those tasks are calling System.exit() or
> Runtime.exit() and aren't forking a new JVM, then when running on Java
> 18 and higher, they may notice that the Ant JVM process gets killed.
> Such builds are recommended to either not call
> System.exit()/Runtime.exit() or use the "fork=true" option in relevant
> tasks (wherever appropriate).
>
> Furthermore, the usage of "<permissions>" type when running on Java 18
> and higher is no longer supported. More details are available in the
> manual of that type https://dist.apache.org/repos/dist/dev/ant/manual/.
>
> The complete set of changes in this release are noted in
> https://dist.apache.org/repos/dist/dev/ant/RELEASE-NOTES-1.10.14.html.
>
> Please do give this proposed release version a try against whichever
> Java runtime versions you plan to use it against (this version requires
> a minimum of Java 8 runtime, like any other Ant 1.10.x versions). Even
> if you don't vote, if you do run into issues, please report back - it
> takes time to create Ant releases, so catching any blocker issues (like
> some of which we saw after Ant 1.10.13 was released) early will help fix
> them sooner.
>
> This vote will be open for at least 72 hours and close no earlier than
> 19th August 2023 12 PM.
>
> -Jaikiran
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@ant.apache.org
> For additional commands, e-mail: dev-help@ant.apache.org
>
>
[RESULT] Release Apache Ant 1.10.14 based on RC1
Posted by Jaikiran Pai <ja...@apache.org>.
With (binding) +1s for Stefan, Maarten, me and Paul (non-binding), this
vote has now passed. I'll now go ahead with the rest of the release process.
Thank you all for the help in moving this release forward.
-Jaikiran
On 16/08/23 6:05 pm, Jaikiran Pai wrote:
> Hello everyone,
>
> I've created RC1 release candidate for Ant 1.10.14 release:
>
> git tag: ANT_1.10.14_RC1
>
> on commit: 53f19eccf49acf526415997046dca5a5135b0e8f
>
> tarballs: https://dist.apache.org/repos/dist/dev/ant/
>
> revision: 63474
>
> Maven artifacts:
> https://repository.apache.org/content/repositories/orgapacheant-1057
>
>
> Apart from regular bug fixes, this 1.10.14 release has crucial changes
> around Ant's usage of Java SecurityManager. Many of you will be aware
> that Java 17 deprecated (for removal) the use of SecurityManager. Java
> 18 then disallowed setting SecurityManager at runtime, by default. Ant
> internally sets a SecurityManager at runtime to prevent System.exit()
> calls from within tasks, from killing the JVM in which Ant process is
> running. In Ant 1.10.13, we tried to keep using the SecurityManager
> internally for a few more releases in Ant, to facilitate projects to
> use Ant without requiring (major) changes to their build. The
> workarounds we put in place in Ant 1.10.13 were brittle and complex
> and although we had hoped they won't break user builds, they did end
> up breaking several builds. Ultimately, these workarounds for usage of
> SecurityManager are no longer feasible or adding value.
>
> As such, this 1.10.14 release of Ant will no longer use (or set) Java
> SecurityManager when running on Java versions 18 and higher. This has
> implications for projects using Ant. Specifically, if any of the build
> tasks (for example the "<java>", "<junit>" or "<junitlauncher>" tasks)
> or libraries used in those tasks are calling System.exit() or
> Runtime.exit() and aren't forking a new JVM, then when running on Java
> 18 and higher, they may notice that the Ant JVM process gets killed.
> Such builds are recommended to either not call
> System.exit()/Runtime.exit() or use the "fork=true" option in relevant
> tasks (wherever appropriate).
>
> Furthermore, the usage of "<permissions>" type when running on Java 18
> and higher is no longer supported. More details are available in the
> manual of that type https://dist.apache.org/repos/dist/dev/ant/manual/.
>
> The complete set of changes in this release are noted in
> https://dist.apache.org/repos/dist/dev/ant/RELEASE-NOTES-1.10.14.html.
>
> Please do give this proposed release version a try against whichever
> Java runtime versions you plan to use it against (this version
> requires a minimum of Java 8 runtime, like any other Ant 1.10.x
> versions). Even if you don't vote, if you do run into issues, please
> report back - it takes time to create Ant releases, so catching any
> blocker issues (like some of which we saw after Ant 1.10.13 was
> released) early will help fix them sooner.
>
> This vote will be open for at least 72 hours and close no earlier than
> 19th August 2023 12 PM.
>
> -Jaikiran
>
---------------------------------------------------------------------
To unsubscribe, e-mail: user-unsubscribe@ant.apache.org
For additional commands, e-mail: user-help@ant.apache.org
Re: [VOTE] Release Apache Ant 1.10.14 based on RC1
Posted by Gary Gregory <gg...@rocketsoftware.com>.
(AFK) Does this remove the class file in the root of the ant-launcher jar which caused JPMS issues? If so, it might be worth mentioning in the release noyes.
Gary
________________________________
From: Jaikiran Pai <ja...@apache.org>
Sent: Wednesday, August 16, 2023 8:35:22 AM
To: user@ant.apache.org <us...@ant.apache.org>; dev@ant.apache.org <de...@ant.apache.org>
Subject: [VOTE] Release Apache Ant 1.10.14 based on RC1
EXTERNAL EMAIL
Hello everyone,
I've created RC1 release candidate for Ant 1.10.14 release:
git tag: ANT_1.10.14_RC1
on commit: 53f19eccf49acf526415997046dca5a5135b0e8f
tarballs: https://dist.apache.org/repos/dist/dev/ant/<https://dist.apache.org/repos/dist/dev/ant>
revision: 63474
Maven artifacts:
https://repository.apache.org/content/repositories/orgapacheant-1057<https://repository.apache.org/content/repositories/orgapacheant-1057>
Apart from regular bug fixes, this 1.10.14 release has crucial changes
around Ant's usage of Java SecurityManager. Many of you will be aware
that Java 17 deprecated (for removal) the use of SecurityManager. Java
18 then disallowed setting SecurityManager at runtime, by default. Ant
internally sets a SecurityManager at runtime to prevent System.exit()
calls from within tasks, from killing the JVM in which Ant process is
running. In Ant 1.10.13, we tried to keep using the SecurityManager
internally for a few more releases in Ant, to facilitate projects to use
Ant without requiring (major) changes to their build. The workarounds we
put in place in Ant 1.10.13 were brittle and complex and although we had
hoped they won't break user builds, they did end up breaking several
builds. Ultimately, these workarounds for usage of SecurityManager are
no longer feasible or adding value.
As such, this 1.10.14 release of Ant will no longer use (or set) Java
SecurityManager when running on Java versions 18 and higher. This has
implications for projects using Ant. Specifically, if any of the build
tasks (for example the "<java>", "<junit>" or "<junitlauncher>" tasks)
or libraries used in those tasks are calling System.exit() or
Runtime.exit() and aren't forking a new JVM, then when running on Java
18 and higher, they may notice that the Ant JVM process gets killed.
Such builds are recommended to either not call
System.exit()/Runtime.exit() or use the "fork=true" option in relevant
tasks (wherever appropriate).
Furthermore, the usage of "<permissions>" type when running on Java 18
and higher is no longer supported. More details are available in the
manual of that type https://dist.apache.org/repos/dist/dev/ant/manual/<https://dist.apache.org/repos/dist/dev/ant/manual>.
The complete set of changes in this release are noted in
https://dist.apache.org/repos/dist/dev/ant/RELEASE-NOTES-1.10.14.html<https://dist.apache.org/repos/dist/dev/ant/RELEASE-NOTES-1.10.14.html>.
Please do give this proposed release version a try against whichever
Java runtime versions you plan to use it against (this version requires
a minimum of Java 8 runtime, like any other Ant 1.10.x versions). Even
if you don't vote, if you do run into issues, please report back - it
takes time to create Ant releases, so catching any blocker issues (like
some of which we saw after Ant 1.10.13 was released) early will help fix
them sooner.
This vote will be open for at least 72 hours and close no earlier than
19th August 2023 12 PM.
-Jaikiran
---------------------------------------------------------------------
To unsubscribe, e-mail: user-unsubscribe@ant.apache.org
For additional commands, e-mail: user-help@ant.apache.org
================================
Rocket Software, Inc. and subsidiaries ? 77 Fourth Avenue, Waltham MA 02451 ? Main Office Toll Free Number: +1 855.577.4323
Contact Customer Support: https://my.rocketsoftware.com/RocketCommunity/RCEmailSupport
Unsubscribe from Marketing Messages/Manage Your Subscription Preferences - http://www.rocketsoftware.com/manage-your-email-preferences
Privacy Policy - http://www.rocketsoftware.com/company/legal/privacy-policy
================================
This communication and any attachments may contain confidential information of Rocket Software, Inc. All unauthorized use, disclosure or distribution is prohibited. If you are not the intended recipient, please notify Rocket Software immediately and destroy all copies of this communication. Thank you.