Hello,
I've been big fan of ERXTimeZoneDetector for years—we stick it in just about
every page wrapper component. Launching under Java 25 prints this to the
console:
WARNING: Use of the three-letter time zone ID "NST" is deprecated and it will
be removed in a future release
WARNING: Use of the three-letter time zone ID "HST" is deprecated and it will
be removed in a future release
... and so on.
Interestingly, it's this loop that does it in ERXTimeZoneDetector.allZones():
String[] ids = TimeZone.getAvailableIDs();
NSMutableArray<TimeZone> tzs = new NSMutableArray<>(ids.length);
for (int i = 0; i < ids.length; i++) {
TimeZone tz = TimeZone.getTimeZone(ids[i]);
tzs.addObject(tz);
}
That is, TimeZone.getAvailableIDs() returns a list that includes IDs that
TimeZone.getTimeZone() then complains about! As annoying as that output to
System.err is, I suspect it's just easiest to ignore it for now. Presumably
when those IDs are finally removed, they won't be returned by getAvailableIDs()
either. So I guess there's no question here, just a public service
announcement, unless "@author Ramsey Gurley" wants to suggest something
different!
--
Paul Hoadley
https://logicsquad.net/
https://www.linkedin.com/company/logic-squad/