That can work for me as well; just not what I was expecting; we did a similar thing to "legacy" code in previous releases. It is a nice way to get classes out of the way where they will not confuse others.
Aside: I have reports of an oracle transaction deadlock on the uDig list; I am asking for a few more details before making a bug report. Jody On 22/09/2010, at 11:36 PM, Andrea Aime wrote: > On 22/09/2010 15:22, Jody Garnett wrote: > > I was thinking they would go through a normal deprecate and remove cycle? > > Hmmm... we could do that and keep the unused garbage around one more > cycle... not what I was hoping for cleanup wise, but I'd be open to > that as well. > Afaik the postgis datastore was not marked as deprecated, > just moved to unsupported, was hoping to do the same for the > old jdbc base classes > > Cheers > Andrea > > > > -- > Andrea Aime > OpenGeo - http://opengeo.org > Expert service straight from the developers. ------------------------------------------------------------------------------ Start uncovering the many advantages of virtual appliances and start using them to simplify application deployment and accelerate your shift to cloud computing. http://p.sf.net/sfu/novell-sfdev2dev _______________________________________________ Geotools-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/geotools-devel
