Details
-
Wish
-
Status: Closed
-
Major
-
Resolution: Duplicate
-
None
-
None
Description
This came up on the commons-user mailing list from Nicolas de Loof. There are a bunch of System.outs in the DBCP code. Currently it depends on c-logging, but only for the test. I'm not usually a fan of adding c-logging to a library, but in DBCPs case I think it's warranted that people are often going to want to be debugging through logs.
Attachments
Issue Links
- duplicates
-
DBCP-4 [dbcp] Use commons-logging for debugging instead of System.out.println
- Closed