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 51746 invoked from network); 11 Sep 2000 10:57:21 -0000 Received: from public.ndh.net (HELO public.ndh.com) (195.94.90.21) by locus.apache.org with SMTP; 11 Sep 2000 10:57:21 -0000 Received: from sbodewig.bost.de ([195.227.98.11]) by public.ndh.com (8.9.3/8.8.0) with ESMTP id MAA16083 for ; Mon, 11 Sep 2000 12:57:18 +0200 (MET DST) Received: (from bodewig@localhost) by sbodewig.bost.de (8.9.3/8.9.3) id MAA04134; Mon, 11 Sep 2000 12:57:20 +0200 X-Authentication-Warning: sbodewig.bost.de: bodewig set sender to bodewig@bost.de using -f To: ant-dev@jakarta.apache.org Subject: Re: Proposed way to make ${} happen at runtime References: From: Stefan Bodewig Date: 11 Sep 2000 12:57:19 +0200 In-Reply-To: Barrie Treloar's message of "Mon, 11 Sep 2000 09:39:16 +0930 (CST)" Message-ID: Lines: 22 User-Agent: Gnus/5.0807 (Gnus v5.8.7) XEmacs/21.1 (Capitol Reef) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Spam-Rating: locus.apache.org 1.6.2 0/1000/N >>>>> "BT" == Barrie Treloar writes: BT> This will break the old way of using the definition order in the BT> file. True - I'd list this in WHATSNEW quite prominently anyway. Do you think this is a real problem - my guess is one would place all tags outside of any targets if one was going to rely on the order of definition. BT> When you specify an id that xml structure is available globaly. BT> Id must be unique in the build.xml file. This has been true before. BT> I'm just being nit picky on the use of {} for all if/else BT> statements even if they are one line bodies. A matter of taste. I tend to write them that way - at least since JDE's abbrev mode added the braces automagically 8^). Stefan