> > If there are any other legitimate reasons - such as - you needed to > > fix some bugs in the code that weren't being addressed in dbcp, then > > you should just put the code in your source control system. > > If this was the problem, the right way to fix it would be to go and help > out DBCP and fix the bugs in the source. This is exactly what happened just > before the latest round of releases to fix > http://issues.apache.org/bugzilla/show_bug.cgi?id=43552 which was caused by > a commons-pool bug.
I realize that, and I'm glad to see that the projects responsive, and work well with each other. But we all know that sometimes that doesn't happen - good project maintainers come and go. Smaller projects don't do well when the good maintainers move on to other work, and you are left with no choice but to fork their code if you want to fix an issue in a timely fashion. > > It seems that at a minimum, you should at least include the refactored > > source code in the source download. > > If you care about this you can always open a bugzilla entry for an > enhancement and propose a patch. I probably will sometime in the near future, when I get caught up again :) Thanks for your patience, I know my initial post was rather a flame bait. Dan --------------------------------------------------------------------- To start a new topic, e-mail: users@tomcat.apache.org To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
