A maintenance release of ICU4J, 3.4.2, was made available on Jan 20th, 2006.
My apologies for the late announcement.
The major changes in this release are:
1) ICU4J 3.4.2 can be built with a switch that lets it run under Java
2) ICU4J 3.4.2 provides its own timezone data, and is independent of the
This release also fixes some urgent bugs. Additional details are below and in
the README that goes out with the release.
Eclipse and Java 1.3 compatibility
The primary driver for this release is to snapshot the version of ICU4J that
will be made available as an Eclipse jar. This required some changes to ICU4J
to meet Eclipse requirements, in particular, the ability to have a version of
ICU4J that runs under a Foundation 1.0 profile. This profile is a subset of JDK
1.3, and omits some functionality and API that the standard version of ICU4J
In order to accomodate this, we use an internal 'preprocessing' tool to tweak
standard ICU4J source files. A dozen or so ICU4J files were marked up so that
the tool could conditionally add or omit APIs and code as required. The Eclipse
version of the ICU4J APIs is therefore somewhat different from the standard
version, while the standard version has not regressed from the previous
ICU Time Zone Data
ICU4J now (once again) uses its own time zone data rather than relying upon the
time zone data in the JDK. This allows users to get current time zone
information even when running on older versions of the JDK.
This release contains the following bug fixes (not a complete list):
# jb4422: RFE: ICU4J should not depend on sun.util.calendar.ZoneInfo
# jb4555: Chinese calendar missing constructor call to setTimeInMillis()
# jb4767: RFE: Provide mechanism for loading Java resources with ULocale
# jb4863: possible rounding bug for currency (Locale=de_CH)
# jb4904: ChineseDateFormat.toLocalizedPattern() throws
java.lang.IllegalArgumentException: Illegal pattern character 'l'
Do You Yahoo!?
Tired of spam? Yahoo! Mail has the best spam protection around