The <property> task is used as a nested task in several places (inside
<ant>/<antcall> for example)... so no, it wouldn't be out of line at all.
Erik
----- Original Message -----
From: "Diane Holt" <[EMAIL PROTECTED]>
To: "Ant Developers List" <[EMAIL PROTECTED]>
Sent: Monday, April 29, 2002 8:05 PM
Subject: A task as a nested element?
> I have some functionality I'd like to add to <pathconvert>, but I think it
> might also be useful on its own right, so... would it be weird, abnormal,
> or (dare I say it?) whacky :) to have a task that could also serve as a
> nested element for another task?
>
> Thanks,
> Diane
>
> =====
> ([EMAIL PROTECTED])
>
>
>
> __________________________________________________
> Do You Yahoo!?
> Yahoo! Health - your guide to health and wellness
> http://health.yahoo.com
>
> --
> To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]>
> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
>
>
--
To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
