On Wed, Jul 10, 2013 at 2:04 PM, Stephen Colebourne <scolebou...@joda.org> wrote: > I think it may be best to have a zip file tagged with the version > inside the jar file. So the jar file only contains the text file and > the zip file.
That sounds good. So... joda-timezone-2013z.jar would be: /org.joda.time.tzdb-verzion.txt OR /org/joda/time/tzdb-version.txt? (I prefer latter, or in tz namespace) /org.joda.time.tzdb-2013z.zip OR /org/joda/time/tzdb-2013z.zip? (latter, or in tz namespace) Loading TZ data scans tzdb-version.txt resources, looks for greatest version, opens up zip from CL resources and loads TZ data. Failing that, it loads shipped data from tz.data namespace (or should we structure that the same way with the same .txt?) > groupId: joda-time > artifactId: joda-time-tzdb > version: tzdb version number > > The trouble is that I only want the new format of jar suitable for > smart loading to be pushed there, rather than a jar that overrides on > the classpath. > > Oh, and only I can push to sonatype OSS at the moment. I can structure the new jar as agreed (above, with clarifications) and prepare it. You can add me to sonatype or push it yourself once I have it ready. The scanning is going to be less complex if we have a versioned .zip to load tzdata from, so it may not take as long to impl (I'm just juggling a few things at once right now). - 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
