You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@commons.apache.org by "Niall Pemberton (JIRA)" <ji...@apache.org> on 2010/12/23 01:48:01 UTC
[jira] Resolved: (IO-254) FileUtils.contentEquals returns true for
equal file names, but file is actually not existing
[ https://issues.apache.org/jira/browse/IO-254?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Niall Pemberton resolved IO-254.
--------------------------------
Resolution: Won't Fix
The main purpose of this method is to compare the contents of files which do exist. It needs to gracefully handle non-existent files, which it does. Its an edge case comparing the content of two non-existent files and you could argue it either way. Its worked this way since IO 1.0 and the comment in the code clearly indicates it was intentional and therefore I don't think we should be changed.
> FileUtils.contentEquals returns true for equal file names, but file is actually not existing
> --------------------------------------------------------------------------------------------
>
> Key: IO-254
> URL: https://issues.apache.org/jira/browse/IO-254
> Project: Commons IO
> Issue Type: Bug
> Environment: windows and linux
> Reporter: Dmitry Kan
> Priority: Trivial
>
> It is said in the documentation, that:
> "This method checks to see if the two files are different lengths or if they point to the same file, before resorting to byte-by-byte comparison of the contents. "
> Does it make sense to return true when the file does not exist even if comparison of a file to itself was attempted?
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.