commons-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Mark Thomas (JIRA)" <j...@apache.org>
Subject [jira] Resolved: (DBCP-4) [dbcp] Use commons-logging for debugging instead of System.out.println
Date Wed, 18 Feb 2009 13:01:02 GMT

     [ https://issues.apache.org/jira/browse/DBCP-4?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Mark Thomas resolved DBCP-4.
----------------------------

    Resolution: Won't Fix

Of the places were System.out is currently used:
- AbandonedObjectpool and AbandonedTrace have been deprecated
- The remaining uses are for the default logWriter which may be replaced if required by the
developer

Therefore, I see no need for any changes to DBCP.

> [dbcp] Use commons-logging for debugging instead of System.out.println
> ----------------------------------------------------------------------
>
>                 Key: DBCP-4
>                 URL: https://issues.apache.org/jira/browse/DBCP-4
>             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 
> "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.
-
You can reply to this email to add a comment to the issue online.


Mime
View raw message