Return-Path: 
 <dev-return-49137-apmail-ant-dev-archive=ant.apache.org@ant.apache.org>
Delivered-To: apmail-ant-dev-archive@ant.apache.org
Received: (qmail 76097 invoked by uid 500); 5 Aug 2003 16:17:28 -0000
Mailing-List: contact dev-help@ant.apache.org; run by ezmlm
Precedence: bulk
List-Unsubscribe: <mailto:dev-unsubscribe@ant.apache.org>
List-Subscribe: <mailto:dev-subscribe@ant.apache.org>
List-Help: <mailto:dev-help@ant.apache.org>
List-Post: <mailto:dev@ant.apache.org>
List-Id: "Ant Developers List" <dev.ant.apache.org>
Reply-To: "Ant Developers List" <dev@ant.apache.org>
Delivered-To: mailing list dev@ant.apache.org
Received: (qmail 76061 invoked from network); 5 Aug 2003 16:17:27 -0000
Received: from unknown (HELO mx1.try.sybase.com) (130.214.10.19)
  by daedalus.apache.org with SMTP; 5 Aug 2003 16:17:27 -0000
Received: from mail.try.sybase.com (mail.try.sybase.com [130.214.10.18])
	by mx1.try.sybase.com (8.11.6/8.11.0) with ESMTP id h75F8E215788
	for <dev@ant.apache.org>; Tue, 5 Aug 2003 09:08:14 -0600
Received: from vpnlinux ([10.22.120.166])
	by mail.try.sybase.com (8.11.6/8.11.6) with SMTP id h75G8SK31822
	for <dev@ant.apache.org>; Tue, 5 Aug 2003 10:08:29 -0600
Reply-To: <ajack@trysybase.com>
From: "Adam Jack" <ajack@trysybase.com>
To: "'Ant Developers List'" <dev@ant.apache.org>
Subject: RE: DataTypes
Date: Tue, 5 Aug 2003 10:17:46 -0600
Message-ID: <003701c35b6d$1c03cd80$a678160a@sybase.com>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook CWS, Build 9.0.2416 (9.0.2910.0)
In-Reply-To: <m3y8y8165y.fsf@bodewig.bost.de>
X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4910.0300
Importance: Normal
X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N

Thanks Stefan, good information, I appreciate it.

>	In principle with Ant 1.2, but <typedef> 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 <typedef> (and perhaps references).

Again, and sorry if it is an FAQ -- but what is the "correct" ant to be
backwards compatible with these days?  1.5? Older?

I have some new tasks I want to publish, and they are heavily into nested
sub-elements, but since I test with 1.6 nightly I could easily have
compatibility problems.

	http://www.krysalis.org/version/ant/index.html

Is there any testing process to determine compatibility level (other than
users... ;-) ;-)

	> 2) What are the primary benefits of DataTypes? Re-use & References?

	In 1.6 there is a whole bunch of new opportunities for them, but let's
	stick with 1.5.x for now.

Mind telling me about 1.6?

	> 3) Ought pretty much all NestedElement be DataTypes -- to be more
	> flexible?

	The only flexibility you gain is that you can define them outside of
	tasks,

Sounds enough "more flexible" for me to want to do this.

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. If there is, and it is cheap for you to let me know, please do,
otherwise I'll dig into example code.

	> 4) I really find this "unfortunate":
	>
	> 	<typedef resource="krysalis-version" />
	> 	<taskdef resource="krysalis-version" />

	Ant 1.6 will change this by using the new antlib concept.

How do I find out about this? I am sure I've missed gobs of stuff on this
list, that is in the archive, so I could start there. That said, is there
any "one stop antlib info shop" I could benefit from, like a design document
or wiki or something?

Thank in advance, and thanks again for the information.

regards

Adam


---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@ant.apache.org
For additional commands, e-mail: dev-help@ant.apache.org