JDK-5054346 : Support tzdata2004a
  • Type: Enhancement
  • Component: core-libs
  • Sub-Component: java.util:i18n
  • Affected Version: 5.0,6
  • Priority: P3
  • Status: Closed
  • Resolution: Fixed
  • OS: generic,windows_xp
  • CPU: generic,x86
  • Submitted: 2004-05-28
  • Updated: 2004-10-04
  • Resolved: 2004-10-04
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 6
6 mustangFixed
Related Reports
Duplicate :  
JDK-6275152 - Calendar.getInstance() gives incorrect time on Asia/Irkutsk, summer time
Relates :  
JDK-5081801 - Support tzdata2004b
Relates :  
JDK-5055567 - (tz) TimeZone.getAvailableIDs(int) may produce inconsistent info with getRawOffset()
Description
The latest Olson zoneinfo data tzdata2004a has been released today.

Changes affecting current time stamps:

* Mendoza, Argentina moved its clocks back this weekend due to an
  emergency law designed to save energy.  (This is unusual, as
  normally clocks are moved forward to save energy, but apparently
  the province uses a lot of electricity in the morning.)  Thanks
  to Mariano Absatz for this item.

* Mongolia does observe daylight-saving time.  Thanks to
  Ganbold Ts. for this item.


Diffs are in the Attachment.

###@###.### 2004-05-28
Comments
CONVERTED DATA BugTraq+ Release Management Values COMMIT TO FIX: mustang FIXED IN: mustang
30-09-2004
EVALUATION TimeZone data in Tiger should be updated. ###@###.### 2004-05-28 This tzdata2004a support breaks a JCK test case due to the built-in assumption on the GMT offsets in getAvailableIDs(int). ###@###.### 2004-06-01
28-05-2004