On 10/02/2011 04:42, Phil Steitz wrote: > I ran into commons-dbcp-all-1.3-r699049.jar on a tomcat host that I > was looking at the other day. Googling led me to openEJB, which > appears to bundle and mirror this jar > (o.a.openejb/commons-dbcp-all). I suspect that what happened is > that they got tired of waiting for dbcp 1.3 and cut a version based > on the revision number above and bundling required classes from pool > 1.3 (at least that's what it looks like from the manifest). My > immediate reaction was to encourage the OpenEJB ppl to upgrade to > the released version of dbcp 1.3 and the latest pool release. This > led to question above. Should we just start providing > commons-dbcp-all?
I'd rather not. I'd prefer we did more frequent releases (he says knowing he has been focussed on Tomcat rather more then commons since the 1.3/1/4 release). > Or should we just point them at release tags to use? That would be better. I'd prefer that they just used the standard jars. Mark --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org For additional commands, e-mail: dev-h...@commons.apache.org
