I have confirmed that this bug is a regression in version 1.5. DateTimeZone.getOffsetFromLocal was totally re-implemented, introducing a much more complex algorithm. Reverting the change fixes the bug.
http://joda-time.svn.sourceforge.net/viewvc/joda-time/trunk/JodaTime/src/java/org/joda/time/DateTimeZone.java?r1=1232&r2=1231&pathrev=1232 Jason Wilson wrote: >> Thanks for the test code. I am fairly sure that this is a bug, although >> I don't know the cause yet. For some reason, it is only affecting this >> time zone - America/New_York and America/Chicago are OK for example. >> > > Thank you. I will try to roll some of my throw-away code into real > unit tests and post them on this list for inclusion in your test > suite. > > -jason > > ------------------------------------------------------------------------- This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2008. http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ _______________________________________________ Joda-interest mailing list Joda-interest@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/joda-interest
