Re: [Geotools-devel] JDBC cleanup, getting rid of some old modules, deprecating others

[Jody G. <jod...@gm...>]

I think we may be able to mark the package-java with a @deprecated?
I like your plan Andrea.

Jody

On 13/03/2010, at 3:04 AM, Andrea Aime wrote:

> Justin Deoliveira ha scritto:
>> 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?
> 
> Right, no, we did not. The question is... have we ever deprecated a
> module? Like, how do we do that, deprecate every class in it?
> 
> I guess that moving a module in unsupported is similar as they
> are not part of the release but they can still be built from
> sources (so it makes things a bit harder than deprecating
> classes leaving them in place).
> 
> One thing that came to mind is: are the new classes a drop
> in replacement for the older ones?
> I know of one regression, the old classes allowed to grab
> the connection for a certain GT Transaction, this allowed
> straight JDBC code to participate in the same transaction
> as GeoTools. The new one do not.
> 
> It's a small change, but something we should do to preserve
> a viable upgrade path.
> 
> Wondering, are there other significant incompatibilities?
> (where significant is, lack of any way to do something that
>  was possible with the old code)
> 
> Cheers
> Andrea
> 
> -- 
> Andrea Aime
> OpenGeo - http://opengeo.org
> Expert service straight from the developers.
> 
> ------------------------------------------------------------------------------
> 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
> Geo...@li...
> https://lists.sourceforge.net/lists/listinfo/geotools-devel