Return-Path: <james.davidson@eng.sun.com>
Mailing-List: contact ant-dev-help@jakarta.apache.org; run by ezmlm
Delivered-To: mailing list ant-dev@jakarta.apache.org
Received: (qmail 83524 invoked from network); 18 Jun 2000 08:17:07 -0000
Received: from mercury.sun.com (192.9.25.1)
  by locus.apache.org with SMTP; 18 Jun 2000 08:17:07 -0000
Received: from shorter.eng.sun.com ([129.144.123.35])
	by mercury.Sun.COM (8.9.3+Sun/8.9.3) with ESMTP id BAA03257
	for <ant-dev@jakarta.apache.org>; Sun, 18 Jun 2000 01:17:09 -0700 (PDT)
Received: from [129.157.164.14] (muc-rem-4.Germany.Sun.COM [129.157.164.14])
	by shorter.eng.sun.com (8.9.3+Sun/8.9.3/ENSMAIL,v1.7) with ESMTP id BAA18672
	for <ant-dev@jakarta.apache.org>; Sun, 18 Jun 2000 01:17:06 -0700 (PDT)
User-Agent: Microsoft-Outlook-Express-Macintosh-Edition/5.02.2022
Date: Sun, 18 Jun 2000 01:15:00 -0700
Subject: Re: [RFE] Richer Task Specification 
From: James Duncan Davidson <james.davidson@eng.sun.com>
To: <ant-dev@jakarta.apache.org>
Message-ID: <B571754A.47F8%james.davidson@eng.sun.com>
In-Reply-To: <85256900.00044EB1.00@d54mta04.raleigh.ibm.com>
Mime-version: 1.0
Content-type: text/plain; charset="US-ASCII"
Content-transfer-encoding: 7bit
X-Spam-Rating: locus.apache.org 1.6.2 0/1000/N

on 6/15/00 5:46 PM, rubys@us.ibm.com at rubys@us.ibm.com wrote:

> How about a new task which subclasses off of javac.  Its init method calls
> super.init(), then super.execute(), then loads and generated class files
> and defines them as new tasks?

Interesting idea.

> Nested taskdef elements, with identical syntax to the current taskdef task,
> could be used to generate the necessary <include> statements on the javac
> and then to define the mapping between classname and task name.  Users
> could obviously add their own <include> statements if necessary.

Could you propose a sample of how this would be stated in XML?

.duncan