[
https://issues.apache.org/jira/browse/IO-386?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16285804#comment-16285804
]
Bernd Eckenfels commented on IO-386:
------------------------------------
You probably can compare it with the size at the beginning. Both seems to be
rather strange, but comparing with the size after copy is less likely to fail
when the file has changed meanwhile. If this is good or bad is a different
question :)
Can you tell us what you need to get fixed?
> FileUtils.doCopyFile uses different methods to check the file sizes
> -------------------------------------------------------------------
>
> Key: IO-386
> URL: https://issues.apache.org/jira/browse/IO-386
> Project: Commons IO
> Issue Type: Bug
> Reporter: Sebb
> Priority: Minor
>
> FileUtils.doCopyFile uses FileChannel.size() to measure the input file length
> at the start, and File.length() to compare the lengths at the end.
> This is inconsistent.
> If there is a good reason for this it should be documented, otherwise it
> should probably use the same method for all the checks.
> [Note: is FileChannel.size() accurate if the file has not been flushed?]
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
