I looked at the file and the GWT code using it and the format seems pretty clear to me. Writing a new tool looks pretty simple, we just have to decide which implementation strategy to choose.
1.) use JDK java.time package to read the tzdata information packaged with Java. Given that JDK is now released every 6 month, this might also be a nice minimum time frame for possibly automated GWT patch releases with new tzdata. Otherwise if we want to update tzdata in GWT outside of JDK releases, the process is a little more complex because we first have to generate a tzdb.dat file to update a JDK installation. To generate that file, we would also need to use the source from the JDK version we use to execute the GWT tool that generates the GWT json files because the tzdb.dat file format might change between JDK versions. 2.) Use Joda Time and their api to read the tzdata information You would need to checkout Joda Time sources, put the new tzdata files into a special package and then build Joda Time. A tool would then depend on that custom build Joda Time and use the Joda Time API to produces the GWT JSON files. Personally I kind of like option 1.) because we could then align automated GWT releases to JDK releases, e.g. one month after JDK release, and the GWT tool could just use standard JDK API without any dependencies. -- J. -- You received this message because you are subscribed to the Google Groups "GWT Contributors" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/google-web-toolkit-contributors/7db2aeda-c4ef-4b20-97c2-506872c0de69%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
