You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@commons.apache.org by "Sebb (JIRA)" <ji...@apache.org> on 2017/04/23 15:38:04 UTC

[jira] [Resolved] (IO-534) FileUtilTestCase.testForceDeleteDir() should not delete testDirectory parent

     [ https://issues.apache.org/jira/browse/IO-534?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Sebb resolved IO-534.
---------------------
       Resolution: Fixed
    Fix Version/s: 2.6

O-534 FileUtilTestCase.testForceDeleteDir() should not delete
testDirectory parent

Project: http://git-wip-us.apache.org/repos/asf/commons-io/repo
Commit: http://git-wip-us.apache.org/repos/asf/commons-io/commit/31e14101
Tree: http://git-wip-us.apache.org/repos/asf/commons-io/tree/31e14101
Diff: http://git-wip-us.apache.org/repos/asf/commons-io/diff/31e14101


> FileUtilTestCase.testForceDeleteDir() should not delete testDirectory parent
> ----------------------------------------------------------------------------
>
>                 Key: IO-534
>                 URL: https://issues.apache.org/jira/browse/IO-534
>             Project: Commons IO
>          Issue Type: Bug
>          Components: Utilities
>            Reporter: Sebb
>             Fix For: 2.6
>
>
> The test case FileUtilTestCase.testForceDeleteDir() has always attempted to delete the testDirectory parent.
> This is wrong; it should not assume that the testDirectory has a parent that can safely be deleted.
> This is why the testDirectory is currently defined as "test/io" when it would make more sense to use a temporary directory under target. It also explains why the "test" directory is left behind when tests complete.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)