Thanks, Jaikiran, for taking this issue to security-dev and for making
changes to ant to reduce the amount of noise.
On 6/28/21 10:22 AM, Jaikiran Pai wrote:
I spent some time on this today and experimented with some sample
build scripts and I noticed that these warning messages are a lot more
I spent some time on this today and experimented with some sample build
scripts and I noticed that these warning messages are a lot more
intrusive in their current form than what I had initially thought or
noticed.
Based on your and one other user's inputs so far, I've raised a
discussion in
Thanks for that explanation, Jaikiran.
On 6/27/21 8:29 PM, Jaikiran Pai wrote:
Hello Rick,
Thank you for this report. We have been watching this area and have
been aware of this issue, including one other user report[1]. I'm just
waiting for things to become a bit more clear on this front bef
Hello Rick,
Thank you for this report. We have been watching this area and have been
aware of this issue, including one other user report[1]. I'm just
waiting for things to become a bit more clear on this front before
coming up with any proposal in the Ant project on how to deal with this.
Cl
Open JDK 17 build 17-ea+28-2534 causes the ant 1.10.6 task to
produce the following warnings when you DON'T fork the JVM:
WARNING: A terminally deprecated method in java.lang.System has been called
WARNING: System::setSecurityManager has been called by
org.apache.tools.ant.types.Permissions (f
