Hi, so it seems we might need to reach an agreement on the embedded db to use.
H2 pros: - frequent releases - fast - already used in GeoWebCache, GeoServer and JGrass - already used in GeoTools modules - can probably use the EPSG sql dumps directly (it has sql compatibility modes for mysql, oracle and postgres, we need to find which one works the best) H2 cons: - one man show JavaDB pros: - supported by Sun - the community version of it, Derby, is not a one man show JavaDB cons: - supported by Sun (pray never to find a bug or you'll wait for the fix for a long long time) - would be an extra dependency for GeoWebCache, GeoServer and JGrass Votes? I'm +1 on H2, +0 on JavaDB, would be more interested in Derby instead if we went down that path. Oh... mind, we can also have both modules I guess, provided we have enough people to back each of them. I think people time would be better spent doing something other than duplicating work, but in the end in OS the discriminator is the will to do something, independent of what kind of duplication that might cause. Cheers Andrea -- Andrea Aime OpenGeo - http://opengeo.org Expert service straight from the developers. ------------------------------------------------------------------------------ Crystal Reports - New Free Runtime and 30 Day Trial Check out the new simplified licensing option that enables unlimited royalty-free distribution of the report engine for externally facing server and web deployment. http://p.sf.net/sfu/businessobjects _______________________________________________ Geotools-devel mailing list Geotools-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/geotools-devel
