commons-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Niall Pemberton (JIRA)" <>
Subject [jira] Commented: (IO-215) FileUtils copy methods swallow date modification failures
Date Thu, 09 Sep 2010 14:03:32 GMT


Niall Pemberton commented on IO-215:

I've used this in the past and what was most important was that the files were copied - it
was *preferable* that the last modified date was preserved, but a small loss of historical
info was not critical.

I accept that your proposal is a valid alternative way of working - but since these methods
have worked this way since at least Commons IO 1.1 then I'm against changing the behaviour
for current implementations.

I have improved the documentation of the current methods regarding their behaviour wrt preserving
the file dates:

> FileUtils copy methods swallow date modification failures
> ---------------------------------------------------------
>                 Key: IO-215
>                 URL:
>             Project: Commons IO
>          Issue Type: Bug
>          Components: Utilities
>            Reporter: Sebb
> FileUtils.doCopyDirectory(..) and .FileUtils.doCopyFile(..) both call the setLastModified()
method, but fail to check if it succeeded or not.
> Surely if the caller has asked for the date to be preserved, failure to do so should
be reported somehow?

This message is automatically generated by JIRA.
You can reply to this email to add a comment to the issue online.

View raw message