JDK-7086489 : File.lastModified should specify accuracy as well as resolution
  • Type: Enhancement
  • Component: core-libs
  • Sub-Component: java.io
  • Priority: P3
  • Status: Closed
  • Resolution: Fixed
  • OS: generic
  • CPU: generic
  • Submitted: 2011-09-02
  • Updated: 2017-05-31
  • Resolved: 2017-05-17
The Version table provides details related to the release that this issue/RFE will be addressed.

Unresolved : Release in which this issue/RFE will be addressed.
Resolved: Release in which this issue/RFE has been resolved.
Fixed : Release in which this issue/RFE has been fixed. The release containing this fix may be available for download as an Early Access Release or a General Availability Release.

To download the current JDK release, click here.
JDK 10 JDK 9
10Fixed 9 b171Fixed
Related Reports
Relates :  
Relates :  
Relates :  
java.io.File says
A long value representing the time the file was last modified, measured in milliseconds since the epoch (00:00:00 GMT, January 1, 1970),

But just because the *units* are milliseconds, doesn't mean that the returned value is necessarily accurate down to the millisecond.  

The File API should clarify the distinction and give the expected accuracy for common platforms.