Return-Path: Delivered-To: apmail-buildr-users-archive@www.apache.org Received: (qmail 50565 invoked from network); 23 Mar 2010 22:26:04 -0000 Received: from unknown (HELO mail.apache.org) (140.211.11.3) by 140.211.11.9 with SMTP; 23 Mar 2010 22:26:04 -0000 Received: (qmail 7237 invoked by uid 500); 23 Mar 2010 22:26:04 -0000 Delivered-To: apmail-buildr-users-archive@buildr.apache.org Received: (qmail 7175 invoked by uid 500); 23 Mar 2010 22:26:04 -0000 Mailing-List: contact users-help@buildr.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: users@buildr.apache.org Delivered-To: mailing list users@buildr.apache.org Received: (qmail 7167 invoked by uid 99); 23 Mar 2010 22:26:04 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 23 Mar 2010 22:26:04 +0000 X-ASF-Spam-Status: No, hits=-0.0 required=10.0 tests=SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: local policy) Received: from [72.249.23.74] (HELO detailedbalance.net) (72.249.23.74) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 23 Mar 2010 22:25:54 +0000 Received: from dhcp-165-124-223-167.nubic.northwestern.edu (dhcp-165-124-223-167.nubic.northwestern.edu [165.124.223.167]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by detailedbalance.net (Postfix) with ESMTPSA id 309A97C2A8 for ; Tue, 23 Mar 2010 22:25:33 +0000 (UTC) Message-Id: From: Rhett Sutphin To: users@buildr.apache.org In-Reply-To: Content-Type: text/plain; charset=US-ASCII; format=flowed; delsp=yes Content-Transfer-Encoding: 7bit Mime-Version: 1.0 (Apple Message framework v936) Subject: Re: Controlling verbosity Date: Tue, 23 Mar 2010 17:25:32 -0500 References: <4dcd15a91003230959v354fbc53qe984a1d460d1bc3a@mail.gmail.com> X-Mailer: Apple Mail (2.936) X-Virus-Checked: Checked by ClamAV on apache.org I like the idea, but I think the environment variable is a bit clumsy and hard to discover. What about a parameter for --trace? buildr --trace # traces everything buildr --trace=tasks # traces just build-related bits -- task executions, things logged with `trace` in buildr & extensions buildr --trace=ant,javac # ups the verbosity for just ant and javac Rhett On Mar 23, 2010, at 5:11 PM, Antoine Toulme wrote: > I'm all for that one. I was for turning javac verbose to off by > default so > this looks more appropriate - more configuration for the ones that > need it. > > On Tue, Mar 23, 2010 at 09:59, Alex Boisvert > wrote: > >> This was brought up in another email but I figured it deserved a >> separate >> thread. >> >> Right now "buildr --trace" turns the verbose fire-hose to full blast. >> This >> means we run "javac -verbose", "ant --trace", "apt -verbose", ... >> which is >> often overwhelming and of little use when you're simply debugging >> Rake-related dependency issues. >> >> One solution would be to selectively turn on the trace switch based >> on the >> task so I was thinking of adding a BUILDR_TRACE environment >> variable that >> would contain a list of comma-separated keywords to control tracing >> behavior, e.g., export BUILDR_TRACE="javac,ant,apt". >> >> Any better ideas? >> >> alex >>