[
https://issues.apache.org/jira/browse/IO-215?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12907629#action_12907629
]
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:
http://svn.apache.org/viewvc?view=revision&revision=995431
> FileUtils copy methods swallow date modification failures
> ---------------------------------------------------------
>
> Key: IO-215
> URL: https://issues.apache.org/jira/browse/IO-215
> 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.
