https://bz.apache.org/bugzilla/show_bug.cgi?id=65381
--- Comment #9 from René Vincent Jansen <rvjan...@xs4all.nl> --- Having been bitten by this last night in JDK 19ea it might be good to advertise this fork=yes a bit more, and as a workaround, maybe release a version that has the default on fork=yes for the java task, as to limit the damage (which for me was a few hours of poking around to find this bug database and reading the not-so convincing correspondence with the Java security team. I maintain the NetRexx compiler and we were impacted heavily by the not really compatible JPMS changes in Java 9. Now this again ... why just not nop-out the implementation and leave people with their own security managers if they want to. I know that the Ant team also must be impacted by this and really cannot help this. But seeing that this was known for half a year at least (we from NetRexx never noticed warnings because we had to compile under Java 8) I think the time to fix this has come, or paste it over the front page of the Ant website in chocolate characters. So for clarity my request: if fixing is hard, please put out a release with fork=yes as a default to save people some time. -- You are receiving this mail because: You are the assignee for the bug.
