Mailing-List: contact issues-help@commons.apache.org; run by ezmlm
Precedence: bulk
Reply-To: issues@commons.apache.org
Date: Sun, 2 Jun 2013 12:08:20 +0000 (UTC)
From: "Sebb (JIRA)" <jira@apache.org>
To: issues@commons.apache.org
Message-ID: <JIRA.12650505.1370174850224.52758.1370174900559@arcas>
In-Reply-To: <JIRA.12650505.1370174850224@arcas>
References: <JIRA.12650505.1370174850224@arcas>
Subject: [jira] [Created] (IO-384) New FileUtils method to copy file which
 might increase in size
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit

Sebb created IO-384:
-----------------------

             Summary: New FileUtils method to copy file which might increase in size
                 Key: IO-384
                 URL: https://issues.apache.org/jira/browse/IO-384
             Project: Commons IO
          Issue Type: New Feature
            Reporter: Sebb


As mentioned in IO-383, FileUtils.doCopyFile caches the file size.

This means that a growing file (e.g. a log file) may cause the method to report failure.

It might be useful to have a method which keeps looping until there is no more input; this should not throw an IOE if the sizes are different.
More data may have been added - or the file truncated - between completing the copy and checking the size.

The method should return the total bytes written; the caller can then check if the count is OK.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira