From dev-return-49177-apmail-ant-dev-archive=ant.apache.org@ant.apache.org Wed Aug 06 10:31:58 2003 Return-Path: Delivered-To: apmail-ant-dev-archive@ant.apache.org Received: (qmail 89265 invoked by uid 500); 6 Aug 2003 10:31:58 -0000 Mailing-List: contact dev-help@ant.apache.org; run by ezmlm Precedence: bulk List-Unsubscribe: List-Subscribe: List-Help: List-Post: List-Id: "Ant Developers List" Reply-To: "Ant Developers List" Delivered-To: mailing list dev@ant.apache.org Received: (qmail 89254 invoked from network); 6 Aug 2003 10:31:57 -0000 Received: from bodewig.bost.de (62.96.16.111) by daedalus.apache.org with SMTP; 6 Aug 2003 10:31:57 -0000 Received: (from bodewig@localhost) by bodewig.bost.de (8.11.6/8.11.6) id h76AVuF11553; Wed, 6 Aug 2003 12:31:56 +0200 X-Authentication-Warning: bodewig.bost.de: bodewig set sender to bodewig@apache.org using -f To: dev@ant.apache.org Subject: Re: DataTypes References: <003701c35b6d$1c03cd80$a678160a@sybase.com> From: Stefan Bodewig Date: 06 Aug 2003 12:31:56 +0200 In-Reply-To: <003701c35b6d$1c03cd80$a678160a@sybase.com> Message-ID: Lines: 34 User-Agent: Gnus/5.0808 (Gnus v5.8.8) XEmacs/21.4 (Portable Code) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N picking up the pieces Peter hasn't already answered. On Tue, 5 Aug 2003, Adam Jack wrote: > Thanks Stefan, good information, I appreciate it. > >> In principle with Ant 1.2, but didn't exist before >> Ant 1.4 (and didn't work properly before 1.5). > > So, let's see. If I make my classes sub-class from DataType, but > don't rely upon folks having to typedef them, then I ought be in > good shape for 1.2 onwards, and users can leverage (and > perhaps references). Note that data-types don't have to extend DataType at all. > Again, and sorry if it is an FAQ -- but what is the "correct" ant to > be backwards compatible with these days? 1.5? Older? Ask your (potential) users 8-) Ant itself tries hard to be compatible with Ant 1.2 (and in larger parts to pre-Ant 1.1). > I will have to investigate is there is an easy way/pattern to allow > something to be a nested sub-element or have reference id, on the > parent element. The "parent" decides which nested elements it will accept. The patterns for that are listed in the "Writing your own task" section (at least for 1.5). The same rules that apply to tasks apply to nested elements of nested elements as well - i.e. the "parent element" defines create/add methods. Stefan --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscribe@ant.apache.org For additional commands, e-mail: dev-help@ant.apache.org