On Tue, Jul 9, 2013 at 9:39 AM, Stephen Colebourne <scolebou...@joda.org> wrote: > Sorry for the delay. I'm concerned that we do this right. What is > really needed is > > - a time-zone data override jar file, similar to what you propose > - some mechanism for the override jar to replace the main time-zone > data if it is newer, and without any extra manual setup steps for the > user > > How were you planning to use the new data files? They wouldn't be > picked up automatically. Or were you just going to rely on them being > earlier in the classpath...
The latter. In the JRuby distribution, we shade it in before joda-time (if we want to update tzdata...not doing that by default right now). I would expect anyone else using it would either do the same or organize classpath to pick up the other files. I think the timezone data artifact should be as simple as possible. Are you contemplating a setup where the data fles are versioned and some property magic specifies the data files to load? - Charlie ------------------------------------------------------------------------------ See everything from the browser to the database with AppDynamics Get end-to-end visibility with application monitoring from AppDynamics Isolate bottlenecks and diagnose root cause in seconds. Start your free trial of AppDynamics Pro today! http://pubads.g.doubleclick.net/gampad/clk?id=48808831&iu=/4140/ostg.clktrk _______________________________________________ Joda-interest mailing list Joda-interest@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/joda-interest
