[jira] Updated: (DBCP-4) [dbcp] Use commons-logging for debugging instead of System.out.println

["Phil Steitz (JIRA)" <ji...@apache.org>]

     [ http://issues.apache.org/jira/browse/DBCP-4?page=all ]

Phil Steitz updated DBCP-4:
---------------------------

    Bugzilla Id:   (was: 30375)
    Fix Version: 1.3

> [dbcp] Use commons-logging for debugging instead of System.out.println
> ----------------------------------------------------------------------
>
>          Key: DBCP-4
>          URL: http://issues.apache.org/jira/browse/DBCP-4
>      Project: Commons Dbcp
>         Type: Bug

>     Versions: Nightly Builds
>  Environment: Operating System: All
> Platform: All
>     Reporter: Alan Tam
>     Priority: Minor
>      Fix For: 1.3
>  Attachments: dbcp-commons-logging-2.patch, dbcp-commons-logging.patch
>
> At the source code of commons-dbcp, some System.out.println() and
> System.err.println() statements can be found, noticeably in the constructor of 
> "java.org.apache.commons.dbcp.AbandonedObjectPool".
> These statements are annoying, because none of the developers want to see these
> messages but they occuplied the precious space in the log files.
> I think it is still appropriate to use this method to emit errors, but for
> normal behavior, we should have an option never seeing them.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira


---------------------------------------------------------------------
To unsubscribe, e-mail: commons-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: commons-dev-help@jakarta.apache.org