Return-Path: Delivered-To: apmail-commons-issues-archive@locus.apache.org Received: (qmail 44904 invoked from network); 3 Apr 2008 12:50:57 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 3 Apr 2008 12:50:57 -0000 Received: (qmail 1170 invoked by uid 500); 3 Apr 2008 12:50:57 -0000 Delivered-To: apmail-commons-issues-archive@commons.apache.org Received: (qmail 712 invoked by uid 500); 3 Apr 2008 12:50:55 -0000 Mailing-List: contact issues-help@commons.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: issues@commons.apache.org Delivered-To: mailing list issues@commons.apache.org Received: (qmail 187 invoked by uid 99); 3 Apr 2008 12:50:54 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 03 Apr 2008 05:50:54 -0700 X-ASF-Spam-Status: No, hits=-2000.0 required=10.0 tests=ALL_TRUSTED X-Spam-Check-By: apache.org Received: from [140.211.11.140] (HELO brutus.apache.org) (140.211.11.140) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 03 Apr 2008 12:50:21 +0000 Received: from brutus (localhost [127.0.0.1]) by brutus.apache.org (Postfix) with ESMTP id 897FC234C0BF for ; Thu, 3 Apr 2008 05:48:24 -0700 (PDT) Message-ID: <1244576612.1207226904562.JavaMail.jira@brutus> Date: Thu, 3 Apr 2008 05:48:24 -0700 (PDT) From: "Jonathan Amir (JIRA)" To: issues@commons.apache.org Subject: [jira] Commented: (DBCP-4) [dbcp] Use commons-logging for debugging instead of System.out.println MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-Virus-Checked: Checked by ClamAV on apache.org [ https://issues.apache.org/jira/browse/DBCP-4?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12585087#action_12585087 ] Jonathan Amir commented on DBCP-4: ---------------------------------- yeah, I vote for fixing this as well. It doesn't make sense that a commons library won't use commons-logging and instead throw its output to stdout or stderr. Very annoying. > [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.