ant-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Dominique Devienne <DDevie...@lgc.com>
Subject RE: <condition> test for a property being true
Date Thu, 18 Apr 2002 13:59:07 GMT
ANT has a few built-in behavior, like the files excluded by copy, and that
would only add some here, to hardcode the list of "true" values to just
true/on/yes. How about allowing to override/extend these defaults, so that:
* Someone on MacOS can easily add **/_* to the default list of excludes?
* Someone from a different country can add its "true" values, e.g. oui/vrai
in French?

More specifically about <istrue>/<isfalse>, thanks Steve, it's a great idea.
--DD

-----Original Message-----
From: Stefan Bodewig [mailto:bodewig@apache.org] 
Sent: Thursday, April 18, 2002 2:04 AM
To: ant-dev@jakarta.apache.org
Subject: Re: <condition> test for a property being true

On Wed, 17 Apr 2002, Steve Loughran <steve_l@iseran.com> wrote:

> Proposal: I knock up a quick <isTrue> and <isFalse> condition pair.

+1 - but you may also want to cover "on", not only "true" and "yes".
See Project#toBoolean.

If you want to make that <istrue property="property-name" />  instead of
<istrue value="${property-name}" /> that is (as you'd simply use
setValue(boolean) and let Ant do the translation otherwise).

Stefan

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

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


Mime
View raw message