Return-Path: Delivered-To: apmail-jakarta-commons-dev-archive@www.apache.org Received: (qmail 79735 invoked from network); 9 Jun 2005 00:08:06 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (209.237.227.199) by minotaur.apache.org with SMTP; 9 Jun 2005 00:08:06 -0000 Received: (qmail 15885 invoked by uid 500); 9 Jun 2005 00:08:03 -0000 Delivered-To: apmail-jakarta-commons-dev-archive@jakarta.apache.org Received: (qmail 15788 invoked by uid 500); 9 Jun 2005 00:08:03 -0000 Mailing-List: contact commons-dev-help@jakarta.apache.org; run by ezmlm Precedence: bulk List-Unsubscribe: List-Help: List-Post: List-Id: "Jakarta Commons Developers List" Reply-To: "Jakarta Commons Developers List" Delivered-To: mailing list commons-dev@jakarta.apache.org Received: (qmail 15750 invoked by uid 99); 9 Jun 2005 00:08:02 -0000 X-ASF-Spam-Status: No, hits=0.2 required=10.0 tests=NO_REAL_NAME X-Spam-Check-By: apache.org Received: from ajax-1.apache.org (HELO ajax.apache.org) (192.87.106.226) by apache.org (qpsmtpd/0.28) with ESMTP; Wed, 08 Jun 2005 17:08:01 -0700 Received: by ajax.apache.org (Postfix, from userid 99) id 67551D3; Thu, 9 Jun 2005 02:07:58 +0200 (CEST) From: bugzilla@apache.org To: commons-dev@jakarta.apache.org Subject: DO NOT REPLY [Bug 35278] New: - Migrating to commons-logging X-Bugzilla-Reason: AssignedTo Message-Id: <20050609000758.67551D3@ajax.apache.org> Date: Thu, 9 Jun 2005 02:07:58 +0200 (CEST) X-Virus-Checked: Checked X-Spam-Rating: minotaur.apache.org 1.6.2 0/1000/N DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG� RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT . 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=35278 Summary: Migrating to commons-logging Product: Commons Version: 1.1 Final Platform: Other OS/Version: All Status: NEW Severity: enhancement Priority: P3 Component: Transaction AssignedTo: commons-dev@jakarta.apache.org ReportedBy: esteban@openbus.org Hi folks, Might I suggest to migrate from LoggerFacade to commons-logging? The reasons would be: 1) It's a commons package 2) Easier integration on almost every project 3) The API user shouldn't have to take care about the logging strategy. I think the API would be much easier to use. I'm asking this because it was pretty hard for me to debug a problem using this package with Jotm. At last, it was a bug in Jotm but I needed to almost rewrite the logging strategy to find it. I made my own branch (backward incompatible) to debug the problem and then restablished the original package. Please let me know your thoughts and I'd be glad to help in the task. Thanks, Esteban -- Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug, or are watching the assignee. --------------------------------------------------------------------- To unsubscribe, e-mail: commons-dev-unsubscribe@jakarta.apache.org For additional commands, e-mail: commons-dev-help@jakarta.apache.org