ant-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Dominique Devienne" <>
Subject Re: <echo> no conditional attribute
Date Wed, 16 Aug 2006 12:59:53 GMT
On 8/16/06, Peter Reilly <> wrote:
> I think that we should go for 2) adding if/unless to all tasks.
> It should have the same support as the if/unless in targets.
> I do not see the need for more complicated condition support
> (at least at the moment).

I would prefer 3. myself (aspect-style interface), for the reason that
I think we can solve the condition-support-for-datatypes issue you

The way I see it, we should not implement condition-aspects at
execution time, but at *configure* time. By that I mean when the
UnknownElements are turned into actual instances of the right
data-type, which unless I'm mistaken is right before the task
executes. What I envision are namespaced-attributes on any
non-<target> or <project> elements that make these elements

It's a bit akin to the UE processing MacroDef performs in fact.

Another reason is that I like my Ant to be extendeable, and the
aspect-approach give me that, to add ubiquitous access to ifTrue, os,
bshIf, etc... inline conditions.

If this doesn't fly, then I'd settle for 1. + 2., or just 2. Thanks, --DD

PS: Note that adding if/unless to <sequential> gives an implicit
<if>-like. I like it myself, and even proposed to it, but this was
voted down by the commiter that left when @author tags were removed
(don't recall his name. He did the property hook, and was a Tomcat

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message