Hi all and sorry for cross-posting. I'd like to propose upgrading the version of h2database in the trunk poms (both geoserver and geotools) to a newer version than the one currently used.
Situation is we've inadvertently been shipping geoserver with two h2 jars, h2-1.1.104.jar and h2-1.1.119.jar. The former used by geotools and geoserver, the later carried over as a transitive dependency from geowebcache. I just discovered the problem while updating geoserver trunk to point to geowebcache snapshot and got a compile error, since gwc now uses some h2 connection pooling with some speed up benefits. Having talked to Andrea and Arne, we've seen that the h2 database format doesn't change between those two versions, so, provided y update the poms on both trunks to use 1.1.119 instead of 1.1.104 and the build doesn't break, can I commit the version upgrade? any concern? TIA, Gabriel -- Gabriel Roldan OpenGeo - http://opengeo.org Expert service straight from the developers. ------------------------------------------------------------------------------ ThinkGeek and WIRED's GeekDad team up for the Ultimate GeekDad Father's Day Giveaway. ONE MASSIVE PRIZE to the lucky parental unit. See the prize list and enter to win: http://p.sf.net/sfu/thinkgeek-promo _______________________________________________ Geotools-devel mailing list Geotools-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/geotools-devel
