commons-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From bugzi...@apache.org
Subject DO NOT REPLY [Bug 30375] New: - Use commons-logging for debugging instead of System.out.println
Date Thu, 29 Jul 2004 07:52:26 GMT
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG 
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://issues.apache.org/bugzilla/show_bug.cgi?id=30375>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND 
INSERTED IN THE BUG DATABASE.

http://issues.apache.org/bugzilla/show_bug.cgi?id=30375

Use commons-logging for debugging instead of System.out.println

           Summary: Use commons-logging for debugging instead of
                    System.out.println
           Product: Commons
           Version: Nightly Builds
          Platform: All
        OS/Version: All
            Status: NEW
          Severity: Minor
          Priority: Other
         Component: Dbcp
        AssignedTo: commons-dev@jakarta.apache.org
        ReportedBy: Tam@SiuLung.com


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.

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


Mime
View raw message