Return-Path: Mailing-List: contact ant-dev-help@jakarta.apache.org; run by ezmlm Delivered-To: mailing list ant-dev@jakarta.apache.org Received: (qmail 4953 invoked from network); 1 Mar 2001 08:49:51 -0000 Received: from bodewig.bost.de (root@195.227.98.11) by h31.sny.collab.net with SMTP; 1 Mar 2001 08:49:51 -0000 Received: (from bodewig@localhost) by bodewig.bost.de (8.9.3/8.9.3) id JAA04016; Thu, 1 Mar 2001 09:49:46 +0100 X-Authentication-Warning: bodewig.bost.de: bodewig set sender to bodewig@apache.org using -f To: ant-dev@jakarta.apache.org Subject: Re: -emacs flag ?? References: <3.0.6.32.20010223163819.0090add0@alphalink.com.au> <3.0.6.32.20010223170054.008b7b10@alphalink.com.au> <3.0.6.32.20010228200404.00867800@alphalink.com.au> <3A9DC3BF.89A0C998@progress.com> From: Stefan Bodewig Date: 01 Mar 2001 09:49:46 +0100 In-Reply-To: "Bill Burton"'s message of "Wed, 28 Feb 2001 22:36:31 -0500" Message-ID: Lines: 41 User-Agent: Gnus/5.0807 (Gnus v5.8.7) XEmacs/21.1 (Cuyahoga Valley) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Spam-Rating: h31.sny.collab.net 1.6.2 0/1000/N Bill Burton wrote: > For whatever reason, some editors either aren't configurable or > people don't know how to configure them to strip Ant's [javac] > prefix so Ant should have greater flexibility in this area to > conditionally remove these prefixes. For the later part - users don't know how to configure their editor, we could easily make the FAQ entries, include sample .*rc files in src/etc and so on. In the emacs case I want to look at the jde-ant.el posted here a while back and maybe commit it to src/etc for example. > So why not support a "logprefix" attribute at the task level by > adding it to the Task class? Then in any task, you can specify > logprefix="no/off/false", etc. and the DefaultLogger class will turn > on "emacs" mode for the duration of that task. One reason, we don't have task level logging yet. This has been requested frequently, so we should add it to the list of requested features for Ant2 (I'll check whether it is already there and add it otherwise). Actually people wanted to adjust the logging verbosity on a task by task level, but prefixing could be an issue as well. Task (or target) level logging attributes would give us a new bunch of build file user versus build file writer issues though (who should have the last word when it comes to verbosity or prefixing, the user IMO). > As an easy way of modifying the attribute settings for tasks, I was > thinking of a scheme whereby properties could be automatically > translated into task attribute settings. Already on the list of requested features * provide support for user defined task configurations - i.e. give users the ability to specify a default value for attributes (always use debug="true" in unless something else has been specified). Could be a CSS like language, could be a element ... Stefan