JDK-4484483 : API: java.util.Date class doesn't specify what calendar system to be used
  • Type: Bug
  • Component: core-libs
  • Sub-Component: java.util:i18n
  • Affected Version: 1.3.0,1.4.0,1.4.1
  • Priority: P3
  • Status: Closed
  • Resolution: Won't Fix
  • OS: generic,windows_xp
  • CPU: generic,x86
  • Submitted: 2001-07-26
  • Updated: 2017-05-16
  • Resolved: 2003-10-11
Related Reports
Duplicate :  
JDK-4624709 - Doc: document Date.toString not supporting BC dates
Duplicate :  
JDK-4485134 - Date.toString uses the format which doesn't distinguish B.C. dates from A.D.ones
Duplicate :  
JDK-4791948 - API: method Date.toString() returns unexpected string
Relates :  
JDK-4482478 - SimpleDateFormat.format() mishandles larger negative times
Relates :  
JDK-4930130 - (cal) Provide Gregorian-only calendar as a Calendar subclass
Description
Currently, it's very implicit in the API doc that the java.util.Date class API assumes the Gregorian and Julian calendar systems for date handling.
Comments
EVALUATION Add defails of date handling should be documented such as: - Dependencies on the Gregorian and Julian calendars - The Julian/Gregorian cutover date - Year numbering in those different calendar systems masayoshi.okutsu@Eng 2001-07-27 For Tiger, Date will be rewritten with a new calendar API (sun private API). It should support only Gregorian as originally designed in 1.0. ###@###.### 2002-08-19 This will not be fixed due to compatibility concerns. The default Gregorian change defined in the GregorianCalendar class will be added to the new Date class implementation. ###@###.### 2003-10-11
11-10-2003