commons-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Joshua Spiewak (JIRA)" <>
Subject [jira] Commented: (DBCP-4) [dbcp] Use commons-logging for debugging instead of System.out.println
Date Wed, 18 Feb 2009 14:15:01 GMT


Joshua Spiewak commented on DBCP-4:

AbandonedObjectpool and AbandonedTrace have been deprecated for at least the same 4.5 years
that this issue has been opened.  A quick look at the 1.3 JIRA issues did not turn up something
replacing them.  You are trading off your desire to not introduce a dependency with the consumers
of the library being forced to use System.out as part of their logging system that they must

> [dbcp] Use commons-logging for debugging instead of System.out.println
> ----------------------------------------------------------------------
>                 Key: DBCP-4
>                 URL:
>             Project: Commons Dbcp
>          Issue Type: Bug
>    Affects 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 
> "".
> 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.
You can reply to this email to add a comment to the issue online.

View raw message