Sounds like a good idea to me. Although did we officially deprecate any of the plugin jdbc modules? Or was that more or less implied when we started shipping the new ones?
On 3/12/10 4:15 AM, Andrea Aime wrote: > Hi, > I'd like to propose some cleanup in JDBC land, in terms of modules. > > At the moment we have the following modules in unsupported, both > 2.6.x and trunk: > mysql > oracle-spatial > > Those two I would simply remove from trunk. They have had their > "deprecation cycle". > > In plugin we still have two stores that have been replaced by > newer jdbc-ng versions: > db2 > postgis > > I guess that since we released the 2.6.x series with them still > in place, we have to keep them there? But I suggest we move > them in unsupported on trunk. > > The library/jdbc module also contains both base classes for the old > and the new jdbc stores. I'm proposing we move all the old classes > in a jdbc-legacy module that we keep in unsupported just for the > sake of db2 and postgis. > > Opinions? > > Cheers > Andrea > -- Justin Deoliveira OpenGeo - http://opengeo.org Enterprise support for open source geospatial. ------------------------------------------------------------------------------ Download Intel® Parallel Studio Eval Try the new software tools for yourself. Speed compiling, find bugs proactively, and fine-tune applications for parallel performance. See why Intel Parallel Studio got high marks during beta. http://p.sf.net/sfu/intel-sw-dev _______________________________________________ Geotools-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/geotools-devel
