[
https://issues.apache.org/jira/browse/IO-276?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13148876#comment-13148876
]
Ron Kuris commented on IO-276:
------------------------------
I forgot to mention that my patch also actually should fix the reported bug by
removing the parent before removing its children.
> "FileUtils#deleteDirectoryOnExit(File)" does not work
> -----------------------------------------------------
>
> Key: IO-276
> URL: https://issues.apache.org/jira/browse/IO-276
> Project: Commons IO
> Issue Type: Bug
> Environment: Commons IO 1.4
> Reporter: nkami
> Priority: Minor
> Attachments: IO-276-r1201108-patch.txt
>
>
> I called this method, but the target directory was not deleted.
> The source of this method is as follows.
> ----------
> private static void deleteDirectoryOnExit(File directory) throws
> IOException {
> if (!directory.exists()) {
> return;
> }
> cleanDirectoryOnExit(directory);
> directory.deleteOnExit();
> }
> ----------
> In other words, this method calls "java.io.File#deleteOnExit" in order of
> "grandchildren -> children -> parent" for files of the target directory
> hierarchy.
> There is following mention in javadoc of "java.io.File#deleteOnExit".
> ----------
> Files (or directories) are deleted in the reverse order that they are
> registered.
> ----------
> Therefore, I think the calling order of "java.io.File#deleteOnExit" should be
> reverse.
> How will be it?
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
