[
https://issues.apache.org/jira/browse/VFS-814?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Luke Wood updated VFS-814:
--------------------------
Description:
{{FtpFileObject.getTimestampMillis}} stores last modification time using
{{{}FTPFile.setTimestamp{}}}.
{{doDetach()}} nulls out the underling {{{}FTPFile{}}}, but doesn't set
{{mdtmSet = false}} this means later calls to
{{FtpFileObject.getTimestampMillis}} fail to refresh mdtm and default to LIST
timestamp.
Suggested fix:
Add {{mdtmSet = false}} to {{FtpFileObject.doDetach()}}
was:
{{FtpFileObject.getTimestampMillis}} stores last modification time using
{{{}FTPFile.setTimestamp{}}}.
{{doDetach()}} nulls out the underling {{{}FTPFile{}}}, but doesn't set
{{mdtmSet = false}} this means later calls to
{{FtpFileObject.getTimestampMillis}} fail to refresh mdtm and default to LIST
timestamp.
Suggested fix:
Add {{mdtm = false}} to {{FtpFileObject.doDetach()}}
> FtpFileObject: re-fetch MDTM after refresh
> ------------------------------------------
>
> Key: VFS-814
> URL: https://issues.apache.org/jira/browse/VFS-814
> Project: Commons VFS
> Issue Type: Bug
> Affects Versions: 2.8.0, 2.9.0
> Reporter: Luke Wood
> Priority: Major
> Labels: easyfix
>
> {{FtpFileObject.getTimestampMillis}} stores last modification time using
> {{{}FTPFile.setTimestamp{}}}.
> {{doDetach()}} nulls out the underling {{{}FTPFile{}}}, but doesn't set
> {{mdtmSet = false}} this means later calls to
> {{FtpFileObject.getTimestampMillis}} fail to refresh mdtm and default to LIST
> timestamp.
> Suggested fix:
> Add {{mdtmSet = false}} to {{FtpFileObject.doDetach()}}
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
