Fix a bug I introduced to SimpleTimeZone with my Calendar.setTimeZone fix.

Our implementations of SimpleTimeZone and Calendar became mutually recursive
for custom time zones when I changed GregorianCalendar.computeFields to use
TimeZone.inDaylightTime --- SimpleTimeZone's implementation of inDaylightTime
creates a GregorianCalendar leading to a stack overflow looking something
like this...

	at java.util.SimpleTimeZone.inDaylightTime(SimpleTimeZone.java:599)
	at java.util.GregorianCalendar.computeFields(GregorianCalendar.java:595)
	at java.util.Calendar.complete(Calendar.java:819)
	at java.util.Calendar.setTimeInMillis(Calendar.java:1319)
	at java.util.GregorianCalendar.<init>(GregorianCalendar.java:339)
	at java.util.GregorianCalendar.<init>(GregorianCalendar.java:325)
	at java.util.SimpleTimeZone.inDaylightTime(SimpleTimeZone.java:599)

I've cut the knot by introducing "Grego" from ICU4J, and rewriting our
SimpleTimeZone.inDaylightTime in the style of ICU4J's implementation.

Maybe we'll be using the ICU4J calendar implementation sooner than I thought!

1 files changed, 1 insertions, 1 deletions

diff --git a/NOTICE b/NOTICE
index f51da455af0..68da3f3ccf4 100644
--- a/NOTICE
+++ b/NOTICE
@@ -59,7 +59,7 @@ SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.
    ==  NOTICE file for the ICU License.                                   ==
    =========================================================================
 
-Copyright (c) 1995-2006 International Business Machines Corporation and others
+Copyright (c) 1995-2009 International Business Machines Corporation and others
 
 All rights reserved.