On 30/07/2013 15:19, Konstantin Kolinko wrote: > 2013/7/26 Mark Thomas <ma...@apache.org>:
>> There is quite a bit of work for DBCP2 as a lot of things have been put >> off got a while (I fixed a 9 year old enhancement request earlier this >> week) as they require API changes. >> >> I've been thinking about this a little more and I think there is another >> option that works better for Tomcat 8. >> >> svn copy and package rename DBCP2 and POOL2 to org.apache.tomcat in the >> same way we have handled Commons BCEL, Codec and FileUpload >> Pros: >> - can make early versions of DBCP2 available for testing with Tomcat 8 >> - simpler build process >> - easier to make source changes (we are going to have to make changes >> because DBCP adds Commons-Logging) >> - can switch to tracking released revision numbers at any point (once >> there is a release to track) >> - option to remove code we don't use >> >> Cons: >> - more work to keep in sync than just changing a version number in a >> property file >> - requires effort to set up >> >> My outline plan is to do this early to middle of next week with a 8.0.x >> release (8.0.0-RC1 to be consistent with how we did 7.0.x) towards the >> end of the week. >> > > I would rather not go that way. > > We already have one pool implementation to maintain here (tomcat-jdbc) > which already lacks attention. I mean, it has a number of unfixed bug > reports in Bugzilla. I have little interest in maintaining tomcat-jdbc. My preference has always been to work on pool2/dbcp2. > If it is too early to release POOL2, DBCP2, may be it is possible to > release Java 7 compatible version of 1.x libraries? > > E.g. DBCP 1.4 + patch = DBCP 1.5. That work is in progress and effectively would result in what we produce with our current patching process. Another option would be to depend on POOL2 and DBCP2 snapshots. Tomcat has depended on DBCP snapshots in the past. I still quite like the svn copy approach but I'll look into snapshots as well. Mark --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org For additional commands, e-mail: dev-h...@tomcat.apache.org
