https://bz.apache.org/bugzilla/show_bug.cgi?id=65381
Bug ID: 65381
Summary: java task without fork=yes shows "WARNING:
java.lang.System::setSecurityManager is deprecated and
will be removed in a future release...." with jd17ea26
Product: Ant
Version: 1.10.9
Hardware: PC
OS: Linux
Status: NEW
Severity: normal
Priority: P2
Component: Core tasks
Assignee: [email protected]
Reporter: [email protected]
Target Milestone: ---
Latest JDK17 early-access build integrated the following change:
https://openjdk.java.net/jeps/411
That deprecated the java security managing with the option for removal.
Having an build.xml file calling the <java> task without using fork=yes seems
to trigger that warning at runtime
Apart from that being something to be fixed eventually it created extra
problems when output of said '<java>' tasked is put into an outputProperty as
then the extra text in that property breaks further processing.
Adding fork=yes to the <java> task target does avoid triggering the problem
Note that JDK17 is likely the next LTS java version
--
You are receiving this mail because:
You are the assignee for the bug.
