JDK-6301287 : Pluggable locale tests fail
  • Type: Bug
  • Component: core-libs
  • Sub-Component: java.util:i18n
  • Affected Version: 6
  • Priority: P3
  • Status: Resolved
  • Resolution: Fixed
  • OS: generic
  • CPU: generic
  • Submitted: 2005-07-25
  • Updated: 2010-07-29
  • Resolved: 2005-08-15
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 b48Fixed
Related Reports
Relates :  
JDK-6300580 - (tz) TimeZone.getDisplayName should not take useDaylightTime() value into account
Relates :  
JDK-6253991 - [Fmt-Da] SimpleDateFormat has built-in assumptions on year formatting and parsing
Relates :  
JDK-6302990 - Backout test/java/text/Format/DateFormat/Bug4322313.java change
Relates :  
JDK-4833268 - API: remove calendar system assumptions from DateFormat/SimpleDateFormat
Description
The following test cases fail after the SimpleDateFormat and TimeZone changes for 4833268, 6253991, and 6300580.

- java/util/PluggableLocale/DateFormatProviderTest.sh: DateFormatProvider tests
- java/util/PluggableLocale/TimeZoneNameProviderTest.sh: TimeZoneNameProvider tests
Comments
EVALUATION - java/util/PluggableLocale/DateFormatProviderTest.sh: DateFormatProvider tests Resource keys for calendar specific date and time formats have been changed for 4833268. - java/util/PluggableLocale/TimeZoneNameProviderTest.sh: TimeZoneNameProvider tests The pluggable locale implementation used the locale value to determine if it should call TimeZone.getDisplayName. However, it's no longer applicable because now locale is always set. Changed SimpleDateFormat.subFormat to take a look at the useDateFormatSymbols flag.
25-07-2005