On Tue, Feb 8, 2022 at 5:53 AM Jaikiran Pai wrote:
> Hello Earl,
>
> On 08/02/22 12:59 am, Earl Hood wrote:
> > How exactly does setting the sysprop for only 18 and 19 allow folks to
> test
> > their stuff? If Ant currently depends on the security manager to
> operate,
> > why not set the
On 2022-02-08, Jaikiran Pai wrote:
> Hello Earl,
> On 08/02/22 12:59 am, Earl Hood wrote:
>> How exactly does setting the sysprop for only 18 and 19 allow folks to test
>> their stuff? If Ant currently depends on the security manager to operate,
>> why not set the sysprop regardless, then
Hello Earl,
On 08/02/22 12:59 am, Earl Hood wrote:
How exactly does setting the sysprop for only 18 and 19 allow folks to test
their stuff? If Ant currently depends on the security manager to operate,
why not set the sysprop regardless, then remove in future when a
replacement API exists?
On 2022-02-07, Jaikiran Pai wrote:
> So the launch scripts (the Linux one and the .bat for Windows one)
> have both been updated to set this system property only for Java 18
> and 19. I expect this to be a temporary thing till the new API is
> available. Once the new API is available, I think we
How exactly does setting the sysprop for only 18 and 19 allow folks to test
their stuff? If Ant currently depends on the security manager to operate,
why not set the sysprop regardless, then remove in future when a
replacement API exists?
Since I work on a project that embeds Ant and uses it
Hello Stefan,
I was planning to send out a mail about this change later tonight. But
good you brought this up. To give some background, the security manager
changes starting Java 18 make it such that setting of the security
manager at runtime now throws an exception, which effectively fails
