Return-Path: <Nico.Seessle@epost.de>
Mailing-List: contact ant-dev-help@jakarta.apache.org; run by ezmlm
Delivered-To: mailing list ant-dev@jakarta.apache.org
Received: (qmail 29266 invoked from network); 24 Oct 2000 00:36:48 -0000
Received: from unknown (HELO mail.epost.de) (64.39.38.70)
  by locus.apache.org with SMTP; 24 Oct 2000 00:36:48 -0000
Received: from ns2000 (149.225.70.155) by mail.epost.de (5.1.051)
        id 39EC55840004537A for ant-dev@jakarta.apache.org;
 Tue, 24 Oct 2000 02:36:22 +0200
Message-ID: <000501c03d52$b302ed60$2a2a2a0a@ns2000>
From: "Nico Seessle" <Nico.Seessle@epost.de>
To: <ant-dev@jakarta.apache.org>
References: <635802DA64D4D31190D500508B9B04104E0F6B@dcsrv0>
 <3.0.6.32.20001024111818.008d3a00@latcs4.cs.latrobe.edu.au>
Subject: Re: Javaworld Article about Ant
Date: Tue, 24 Oct 2000 02:38:15 +0200
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 5.00.2919.6700
X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2919.6700
X-Spam-Rating: locus.apache.org 1.6.2 0/1000/N

----- Original Message -----
From: "Peter Donald" <donaldp@locus.apache.org>
To: <ant-dev@jakarta.apache.org>
Sent: Tuesday, October 24, 2000 3:18 AM
Subject: Re: Javaworld Article about Ant


> how about ?
>
>   <taskdef name="function" language="javascript">
>       <![CDATA[
>         myProject.log('arg1: ' + arg1);
>       ]]>
>   </taskdef>
>

It was not intended for posting now (Just posted it in case someone would
like to play arounf with it) and would make it hard for me (as a
not-experienced cvs-user) to have something like this in Taskdef.java and
update local sourced thru cvs. That would be something that *can* be
discussed once Ant 1.2 is out (although I don't personally think a change
like this at such a low level would be accepted for general use). Internally
it does just this: project.addTaskDefinition(name, this.getClass()).

The Problem is (would could be possible to solve in another way with larger
modifications) that you *must* provide a class to ant which is instantiated
and it's attributes are set thru introspection while parsing the relevant
parts of the build.xml. The task currently does both, define a new task if
called with a name "function" and execute a previous defined task (script)
if call with another name.

So all it's current implementation is for simplicity and to require no
changed to ant at all.

Nico