ant-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Dominique Devienne" <DDevie...@lgc.com>
Subject RE: repository
Date Tue, 16 Nov 2004 17:09:18 GMT
> From: Steve Loughran [mailto:stevel@apache.org]
> 
> Which is precisely why every policy has an if attribute that is
boolean
> 
> <force if="${force.update}"/>
> <schedule hours="3" />

Hmmm, the old if/unless debate...

And we keep on littering the Ant code with duplicated if/unless
attributes and the logic/doc associated to them instead of doing it once
and for all in the framework. It would be trivial to ignore in the
UnknownElement of tasks/types all XML elements who's if/unless
attributes makes them irrelevant, since everything done's just in time
now, at runtime, when the values of if/unless can be evaluated. You get
a simple and powerful conditional everywhere. It's akin to <xsl:if>
where the build file is also it's own stytesheet, and almost like
#ifdef. Ah well, it's a lost cause... --DD

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@ant.apache.org
For additional commands, e-mail: dev-help@ant.apache.org


Mime
View raw message