RFR java.time cleanup of javadoc and messages
Xueming Shen
xueming.shen at oracle.com
Mon Feb 3 22:55:49 UTC 2014
The changeset looks fine. But, do we need a CCC for 8032558 and 8032494 "for the
record"?
-Sherman
On 02/03/2014 02:43 PM, roger riggs wrote:
> Please review this group of java.time updates:
>
> 8032749 <https://bugs.openjdk.java.net/browse/JDK-8032749>: Typo in java.time.Clock
> 8032888 <https://bugs.openjdk.java.net/browse/JDK-8032888>: Error message typo in TemporalAccessor
> 8032558 <https://bugs.openjdk.java.net/browse/JDK-8032558>: Instant spec includes incorrect assertion wrt valid range
> 8032494 <https://bugs.openjdk.java.net/browse/JDK-8032494>: DateTimeFormatter spec includes irrelevant detail on parsing pattern
>
> Webrev:
> http://cr.openjdk.java.net/~rriggs/webrev-typos-8032749/
>
> Thanks, Roger
>
More information about the core-libs-dev
mailing list