What if we put the DbConfigGui and PoolConfig classes back in, but made them "deprecated" and always disabled. That way, people could at least load them and copy/paste their info from it to the new element. And do something to prevent these element from showing up in dropdowns - some sort of isDeprecated method or something like that.
I think that might be easier than trying to do something smarter automatically. -Mike On Fri, 2005-09-02 at 15:15 +0100, sebb wrote: > I'm assuming we need to fix the JDBC test plan bug: > > http://issues.apache.org/bugzilla/show_bug.cgi?id=36449 > > for 2.1.1. > > I've made some progress on this, but the upgrade.properties changes > aren't yet complete - indeed I'm not sure that it can handle the > merging of two JDBC config elements. Might need to handle JDBC > specially... > > Anything else vital? > > S. > On 02/09/05, Peter Lin <[EMAIL PROTECTED]> wrote: > > Once we get a patched release of 2.1 out, I want to merge the include > > controller to the 2.1 branch so that people can use it without jdk1.5. > > > > peter > > > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
