On 10 July 2013 18:21, Charles Oliver Nutter <head...@headius.com> wrote: > A question arises... > > I assume we want the compiled data to be structured the same as it is > now, in separate files. So then...once we've found the most recent > tzdb-version file, how to proceed? > > * Data files tagged with version as well; load data files + version appended. > * Data files named as today; use tzdata-version.txt classloader URL > base to load them. > * Something else.
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. >>> You should be able to fork JodaOrg/joda-time on GitHub to your own >>> namespace and work there. That works because you'll need to edit >>> joda-time itself to do the resource file searching. >>> >>> If you need a separate repo to fork from for the time zone db file >>> publishing, I can sort that. > > On second thought...in the interest of time, I'd like to get JRuby off > the current tzdata setup and on to the actual artifact. Can we sort > out a repo, artifact, and release for the data first, and I'll work in > the smart loading after that? 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. Stephen ------------------------------------------------------------------------------ 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
