Rob Atkinson ha scritto: > Justin Deoliveira wrote: >> Perhaps, but writing new code for all of this is easier said then done, >> especially for jdbc. Those modules in particular are built around >> special cases. In rewriting and fixing a lot of the issues, one has to >> be careful to maintain all of the special cases. >> >> Plus the change effects not only postigs, but all the other jdbc >> modules, so it requires agreement from all the jdbc module maintainers >> as well. >> > This is perhaps the bit I have a problem understanding. If we have > deprecated an API, then the other module maintainers are affected > anyway, and to make progress they need to have jdbc fixed, or to move > away from common code. Wearing a hat of a module maintainer, dependent > on jdbc, asking for my agreement is actually a bit disempowering - I > should either maintain my module or see it put into unsupported land or > out of the build entirely. > > To make a decision, I need an assessment of the effort, and an upgrade > path, bith of which really only exist once someone has done the updates.
Rob, I agree with your assessment. +1 :-) Cheers Andrea ------------------------------------------------------------------------- Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys - and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV _______________________________________________ Geotools-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/geotools-devel
