8193072: File.delete() should remove its path from DeleteOnExitHook.files
jason_mehrens at hotmail.com
Tue Jul 9 21:26:58 UTC 2019
Would the SecurityManager need to for permissions (checkWrite or some new permission) before cancelDeleteOnExit() is allowed?
From: core-libs-dev <core-libs-dev-bounces at openjdk.java.net> on behalf of Brian Burkhalter <brian.burkhalter at oracle.com>
Sent: Tuesday, July 9, 2019 1:08 PM
Subject: Re: 8193072: File.delete() should remove its path from DeleteOnExitHook.files
> On Jul 9, 2019, at 8:31 AM, Brian Burkhalter <brian.burkhalter at oracle.com> wrote:
>> Since deleteOnExit() is an deliberate act, perhaps there should be a corresponding withdrawDeleteOnExit() that reverses it so that it is intentional and not a side-effect of other File methods.
> I think this is a better idea. Perhaps “cancelDeleteOnExit()”.
If we want to go this route, here is one possibility:
Of course a CSR would be called for if this is agreed upon.
More information about the core-libs-dev