JDK-8180428 : Clarify implementation note in Clock.java to match implementation changes made by JDK-8068730
  • Type: Bug
  • Component: core-libs
  • Sub-Component: java.time
  • Affected Version: 9
  • Priority: P3
  • Status: Closed
  • Resolution: Fixed
  • Submitted: 2017-05-16
  • Updated: 2017-06-27
  • Resolved: 2017-05-23
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 b172Fixed
Related Reports
Relates :  
Description
In JDK 9, the implementation of Clock has been improved to be better
than millisecond in most cases. However, the Javadoc of the "Implementation Note" is now wrong. It says:

"The clock implementation provided here is based on
System.currentTimeMillis(). That method provides little to no
guarantee about the accuracy of the clock. Applications requiring a
more accurate clock must implement this abstract class themselves
using a different external clock, such as an NTP server."

This needs to be updated to match the changes to the implementation.
Suggested replacement text:

"The clock implementation provided here is based on the same
underlying clock as System.currentTimeMillis(), but may have a
precision finer than milliseconds if available. However, little to no
guarantee is provided about the accuracy of the underlying clock. 
Applications requiring a more accurate clock must implement this
abstract class themselves using a different external clock, such
 as an NTP server."

Comments
See also: http://mail.openjdk.java.net/pipermail/core-libs-dev/2017-May/047671.html
18-05-2017