Return-Path: Delivered-To: apmail-ant-dev-archive@www.apache.org Received: (qmail 80299 invoked from network); 21 Nov 2006 15:07:40 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 21 Nov 2006 15:07:40 -0000 Received: (qmail 95149 invoked by uid 500); 21 Nov 2006 15:07:48 -0000 Delivered-To: apmail-ant-dev-archive@ant.apache.org Received: (qmail 95112 invoked by uid 500); 21 Nov 2006 15:07:48 -0000 Mailing-List: contact dev-help@ant.apache.org; run by ezmlm Precedence: bulk List-Unsubscribe: List-Help: List-Post: List-Id: "Ant Developers List" Reply-To: "Ant Developers List" Delivered-To: mailing list dev@ant.apache.org Received: (qmail 95101 invoked by uid 99); 21 Nov 2006 15:07:48 -0000 Received: from herse.apache.org (HELO herse.apache.org) (140.211.11.133) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 21 Nov 2006 07:07:48 -0800 X-ASF-Spam-Status: No, hits=-0.0 required=10.0 tests=SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (herse.apache.org: domain of ddevienne@gmail.com designates 66.249.92.172 as permitted sender) Received: from [66.249.92.172] (HELO ug-out-1314.google.com) (66.249.92.172) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 21 Nov 2006 07:07:35 -0800 Received: by ug-out-1314.google.com with SMTP id m3so1436865ugc for ; Tue, 21 Nov 2006 07:07:13 -0800 (PST) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=WuYkTfQ/LyLS6yD15e/ORTGmGgUPq4q3cVmpEHkil02/cSr+d3NszCbuqvBq7SK7ePSzYZVu5/B8DjgadMEc9gXJJLqgTfsH7ckTRmjrV2B77afYoKwiXa5WHBiKzgmQYpGorTIxrK9ga+NVelDisdC8pNttjdK6xjPWnm3Pq3k= Received: by 10.78.51.9 with SMTP id y9mr6513630huy.1164121633032; Tue, 21 Nov 2006 07:07:13 -0800 (PST) Received: by 10.78.178.3 with HTTP; Tue, 21 Nov 2006 07:07:12 -0800 (PST) Message-ID: <255d8d690611210707l583388d0pf05f51b5ede3fc23@mail.gmail.com> Date: Tue, 21 Nov 2006 09:07:12 -0600 From: "Dominique Devienne" To: "Ant Developers List" Subject: Re: Bug 32897 In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline References: X-Virus-Checked: Checked by ClamAV on apache.org > >I'm not following. Is such a file automatically loaded? Or are > >you saying to auto-load these properties from the CLI? Can > >that specify the logger and listerners to use? --DD > > The "problem" with the current build.properties is, that it's loaded > from within the buildfile > and you cant add additional listeners (or am I wrong here?). I don't think you are, and it's indeed problematic. > So instead of typing > ant -listener org.apache.tools.ant.listener.Log4jListener > you could just type > ant > and having a ant.logger.properties with > logger=org.apache.tools.ant.listener.Log4jListener > log4j.rootLogger=ERROR, LogFile > log4j.logger.org.apache.tools.ant.Project=INFO > [... http://ant.apache.org/manual/listeners.html#Log4jListener ] > > The Launcher which will automatically load these settings and adds the > logger/listeners as it would be configured on commandline. OK, sounds like you are proposing to do this. I wasn't sure earlier whether you referred to existing behavior I had missed, or new proposed behavior. An alternative to auto-magically loading a properties file might be to add support for the usual @file syntax on the CLI, where long command line args with lots of properties can be easily added. This keeps it explicit, and there are still the existing env. vars. mechanism to automate the specification of @file if one wants. What do you think? --DD --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscribe@ant.apache.org For additional commands, e-mail: dev-help@ant.apache.org