The currently public specification of java.io.File#lastModified() as given below is ambiguous if the last-modified time of an actually extant file is exactly the epoch because the return value would per the specification indicate that the file does not exist.
Returns:
A long value representing the time the file was last modified, measured in milliseconds since the epoch (00:00:00 GMT, January 1, 1970), or 0L if the file does not exist or if an I/O error occurs
Throws:
SecurityException - If a security manager exists and its SecurityManager.checkRead(java.lang.String) method denies read access to the file
Returns:
A long value representing the time the file was last modified, measured in milliseconds since the epoch (00:00:00 GMT, January 1, 1970), or 0L if the file does not exist or if an I/O error occurs
Throws:
SecurityException - If a security manager exists and its SecurityManager.checkRead(java.lang.String) method denies read access to the file
- duplicates
-
JDK-6791812 (file spec) Incompatible File.lastModified() and setLastModified() for negative time
- Closed
- relates to
-
JDK-7086489 File.lastModified should specify accuracy as well as resolution
- Closed
- links to