Hi! > has anybody an idea why date/time conversion on our hudson server > works different than on my windows box? Is there any know > incompatibility across different OSes? > > -Juergen >
The reason is that joda time is caching the default timezone. Wicket datetime is sometimes using MutableDateTime constructors without timezone parameters. In this case it is using the default timezone. But it is cached in joda time and even by first lookup it is first trying to load it trough a system property (see org.joda.time.DateTimeZone.getDefault()). The reason why it worked on your (or my) computer because the new default timezone (Europe/Berlin) had the same time offset as the orignal jvm default (+1 hour). On the hudson server the jvm original default timezone is -4 hours (based on the logs seen on hudson web interface). I made a patch that adds a new test case to show this. First it looks up a timezone that is different from current default than it sets it as new default. The joda default timezone does not change. I am attaching the patch. I hope it is possible to send attached files to the mail list. Attila Király -- "I would rather write programs to write programs than write programs."
