Return-Path: <JFernandez@viquity.com>
Mailing-List: contact ant-dev-help@jakarta.apache.org; run by ezmlm
Delivered-To: mailing list ant-dev@jakarta.apache.org
Received: (qmail 83340 invoked from network); 19 Sep 2000 22:15:13 -0000
Received: from postbox.viquity.com (HELO dcsrv0.ecom2ecom.com)
 (63.198.126.137)
  by locus.apache.org with SMTP; 19 Sep 2000 22:15:13 -0000
Received: by dcsrv0 with Internet Mail Service (5.5.2650.21)
	id <SGY31T26>; Tue, 19 Sep 2000 15:14:39 -0700
Message-ID: <635802DA64D4D31190D500508B9B04104E0F01@dcsrv0>
From: Jose  Alberto Fernandez <JFernandez@viquity.com>
To: "'ant-dev@jakarta.apache.org'" <ant-dev@jakarta.apache.org>
Subject: RE: Lazy evaluation of custom taskdefs
Date: Tue, 19 Sep 2000 15:14:39 -0700
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2650.21)
Content-Type: text/plain;
	charset="iso-8859-1"
X-Spam-Rating: locus.apache.org 1.6.2 0/1000/N

The way to solve this is to put your <taskdef> declaration
inside the <target> that builds yor <task> and then
make the targets that use it to be dependant on that target.

I am doing that right now and it works just great.

Jose Alberto

> -----Original Message-----
> From: Mads Andersen [mailto:mads054@pop.k-net.dk]
> Sent: Tuesday, September 19, 2000 11:34 AM
> To: ant-dev@jakarta.apache.org
> Subject: Lazy evaluation of custom taskdefs
> 
> 
> Now that Ant can finally find my custom tag, I have a minor 
> suggestion.
> 
> My build.xml has a custom task in the beginning of the file 
> as follows:
> 
>   <taskdef name="transform"
> classname="com.madsie.util.xsl.XSLTransformTask"/>
> 
> Now, XSLTransformTask is a part of the project, so after an 
> "ant clean" the
> XSLTransformTask.class is no longer accessible. No matter 
> which target you
> try with Ant, it will fail because the Class of 
> XSLTransformTask is resolved
> before any targets get executed.
> 
> What I would like is to make my targets using taskdef 
> transform ensure that
> XSLTransformTask.java is compiled. This would be possible if 
> custom taskdefs
> were evaluated in a lazy fasion, that is when the custom 
> tasdef is first
> needed.
> 
> Best regards, Madsie
>