DST is not picked up by Java 5 on Solaris (1.4.2 and 5 on Windows are fine)

Question

Solaris 9:
Java 5 ignores daylight savings time and displays time incorrectly. Java 1.4.2 installed on the same Solaris machine displays time zone and time correctly (taking into account DST). Does anybody know what should be tweaked so JRE 1.5 gets DST settings from OS?
Thank you,
Dima.
import java.util.Date;
import java.util.TimeZone;
public class testtime {
  public static void main (String argv[] ) {
    System.out.println ("Time: " + new Date()  + " Time zone: " + TimeZone.getDefault()) ;
}bash-2.05$ echo $TZ
bash-2.05$
bash-2.05$ date
Thu Sep 15 16:36:37 GMT 2005
bash-2.05$ /disk2/ic/iccommon/jre/bin/java -version
java version "1.5.0_04"
Java(TM) 2 Runtime Environment, Standard Edition (build 1.5.0_04-b05)
Java HotSpot(TM) Client VM (build 1.5.0_04-b05, mixed mode)
bash-2.05$ /disk2/ic/iccommon/jre/bin/java -cp . testtime
Time: Thu Sep 15 15:37:47 GMT-05:00 2005 Time zone: sun.util.calendar.ZoneInfo[id="GMT-05:00",offset=-18000000,dstSavings=0,useDaylight=false,transitions=0,lastRule=null]
Java 1.4.2 recognizes daylight savings time correctly:
bash-2.05$
bash-2.05$ /disk1/3PTYSW/java1_4_2_03/bin/java -version
java version "1.4.2_03"
Java(TM) 2 Runtime Environment, Standard Edition (build 1.4.2_03-b02)
Java HotSpot(TM) Client VM (build 1.4.2_03-b02, mixed mode)
bash-2.05$ /disk1/3PTYSW/java1_4_2_03/bin/java -cp . testtime
Time: Thu Sep 15 16:39:20 EDT 2005 Time zone: sun.util.calendar.ZoneInfo[id="US/Eastern",offset=-18000000,[b]dstSavings=3600000,useDaylight=true,transitions=235,lastRule=java.util.SimpleTimeZone[id=US/Eastern,offset=-18000000,dstSavings=3600000,useDaylight=true,startYear=0,startMode=3,startMonth=3,startDay=1,startDayOfWeek=1,startTime=7200000,startTimeMode=0,endMode=2,endMonth=9,endDay=-1,endDayOfWeek=1,endTime=7200000,endTimeMode=0]]
bash-2.05$

Answer 1

Well, they wouldn't rewrite their 1.4 documents at all actually.
This is just Sun improving their product's documentation. Defining a serialVersionUID has always been a good idea, as all versions of the Serialization Specification show.