Return-Path: Delivered-To: apmail-lenya-user-archive@www.apache.org Received: (qmail 8547 invoked from network); 22 Aug 2006 04:09:35 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (209.237.227.199) by minotaur.apache.org with SMTP; 22 Aug 2006 04:09:35 -0000 Received: (qmail 47706 invoked by uid 500); 22 Aug 2006 04:09:35 -0000 Delivered-To: apmail-lenya-user-archive@lenya.apache.org Received: (qmail 47679 invoked by uid 500); 22 Aug 2006 04:09:34 -0000 Mailing-List: contact user-help@lenya.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: user@lenya.apache.org Delivered-To: mailing list user@lenya.apache.org Received: (qmail 47668 invoked by uid 99); 22 Aug 2006 04:09:34 -0000 Received: from asf.osuosl.org (HELO asf.osuosl.org) (140.211.166.49) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 21 Aug 2006 21:09:34 -0700 X-ASF-Spam-Status: No, hits=1.0 required=10.0 tests=DNS_FROM_RFC_ABUSE,NO_REAL_NAME,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (asf.osuosl.org: domain of solprovider@gmail.com designates 64.233.166.181 as permitted sender) Received: from [64.233.166.181] (HELO py-out-1112.google.com) (64.233.166.181) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 21 Aug 2006 21:09:33 -0700 Received: by py-out-1112.google.com with SMTP id s49so2571575pyc for ; Mon, 21 Aug 2006 21:09:13 -0700 (PDT) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:sender:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references:x-google-sender-auth; b=WLekriur06uDJ2//wWiVxTYVHRhqnMqNU0lZXW1BVJaiPCz4sVEMt7skiJ3oELp3/6+1ShpOteG4VeOKP89eBZK6dYnO23eEVuJTumGZK/HJze5QuDKXkgBLw9u0Su22rmmyHUeZC0Cy/LI+67RXhP7SRepFb0pOQjLL7qF712M= Received: by 10.35.63.2 with SMTP id q2mr14698788pyk; Mon, 21 Aug 2006 21:09:13 -0700 (PDT) Received: by 10.35.38.12 with HTTP; Mon, 21 Aug 2006 21:09:13 -0700 (PDT) Message-ID: Date: Tue, 22 Aug 2006 00:09:13 -0400 From: solprovider@apache.org Sender: solprovider@gmail.com To: user@lenya.apache.org Subject: Re: how does log4j logging work? In-Reply-To: <44E9A68B.4030603@uni-due.de> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <44E9A68B.4030603@uni-due.de> X-Google-Sender-Auth: 92890d5c129caffe X-Virus-Checked: Checked by ClamAV on apache.org X-Spam-Rating: minotaur.apache.org 1.6.2 0/1000/N On 8/21/06, Joern Nettingsmeier wrote: > can anyone explain how to do the following?: > * dump all log levels to the console when running tests? (i need this to > chase a problem with andreas' repository migration test) FILE: build/lenya/webapp/WEB-INF/log4j.xconf CHANGE: TO: CHANGE: TO: > * redirect specifig loggers to files Maybe you can now figure it out from reading that file. I am better with log4j.properties, and a quick attempt at adding a file logger did not work. I could not decide if the category name should be a class name or a logger name. The example implies it is a class name, but everything I know says it should be a logger name. solprovider --------------------------------------------------------------------- To unsubscribe, e-mail: user-unsubscribe@lenya.apache.org For additional commands, e-mail: user-help@lenya.apache.org