Here's more on <taskdef> in Ant. Long story short - looks like CVS HEAD things are ok, but with Ant 1.5.x we're stuck with this quirk.

Use <taskdef> in the <target> and all is well :)

Erik

Begin forwarded message:

From: Stefan Bodewig <[EMAIL PROTECTED]>
Date: Fri Apr 4, 2003 1:41:25 AM US/Eastern
To: [EMAIL PROTECTED]
Subject: Re: Fwd: [Xdoclet-user] multiple jsptaglib nested tag in webdoclet
Reply-To: "Ant Developers List" <[EMAIL PROTECTED]>


On Thu, 3 Apr 2003, Erik Hatcher <[EMAIL PROTECTED]>
wrote:

Any ideas on the differences between using <taskdef> under project
or under a target?

Several, and they vary with the Ant version in use.


With Ant 1.5.x, the main difference is that taskdefs defined at the
project level will get evaluated immediately, so Ant creates the
"real" task objects and real nested elements at parser time.  If you
put the taskdef into a target, things go the UnknownElement route
first.  This causes several differences.

With CVS HEAD, things have become different, and <taskdef> is supposed
to work consistently now (unchecked 8-) - as all tasks will be
UnknowElement until used now.

With Ant 1.4, nested child elements didn't work properly in one of the
two cases, can't exactly remember which.

Stefan

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]





-------------------------------------------------------
This SF.net email is sponsored by: ValueWeb: Dedicated Hosting for just $79/mo with 500 GB of bandwidth! No other company gives more support or power for your dedicated server
http://click.atdmt.com/AFF/go/sdnxxaff00300020aff/direct/01/
_______________________________________________
xdoclet-user mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/xdoclet-user

Reply via email to