| Issue | Fix Version | Assignee | Priority | Status | Resolution | Resolved In Build |
|---|---|---|---|---|---|---|
| JDK-8045637 | 8u25 | Roger Riggs | P3 | Resolved | Fixed | b01 |
| JDK-8040032 | 8u20 | Roger Riggs | P3 | Resolved | Fixed | b11 |
| JDK-8053865 | emb-8u26 | Roger Riggs | P3 | Resolved | Fixed | b17 |
The class-level Javadoc spec for DateTimeFormatter includes two sentences: "When parsing in strict mode, the number of parsed digits must match the count of pattern letters. When parsing in lenient mode, the number of parsed digits must be at least the count of pattern letters, up to 9 digits." These two sentences do not make sense in context as there is no way to control whether the pattern is strict or lenient from the DateTimeFormatter class.
Retaining these in the spec could hamper changes in update releases as it implies control or behaviour that cannot be provided through this particular API method.
The solution is to remove the two sentences.
While making this change, line 463 of DateTimeFormatter contains a broken link to the resolve method in TemporalField which should also be fixed.
Retaining these in the spec could hamper changes in update releases as it implies control or behaviour that cannot be provided through this particular API method.
The solution is to remove the two sentences.
While making this change, line 463 of DateTimeFormatter contains a broken link to the resolve method in TemporalField which should also be fixed.
- backported by
-
JDK-8040032 DateTimeFormatter spec includes irrelevant detail on parsing pattern
-
- Resolved
-
-
-
- Resolved
-
-
-
- Resolved
-
- relates to
-
JDK-8031085 DateTimeFormatter won't parse dates with custom format "yyyyMMddHHmmssSSS"
-
- Resolved
-