Yay! :). This is good. Thanks for sharing this information.
On 9/24/2009 3:57 PM, Stefan Bodewig wrote:
On 2009-09-24, Francis GALIEGUE wrote:
But ideally, I'd like to use these properties all the time, with
boolean values. Say, for example, if I have nomail set to 1 or true,
then no mail
On Thu, Sep 24, 2009 at 16:41, danson wrote:
> Both antcontrib[1] and antelope[2] provide if/else constructs. Either
> of these would work for your situation.
>
> Dale
>
> [1] http://ant-contrib.sourceforge.net
> [2] http://antelope.tigris.org
>
>
I know this, I use ant-contrib extensively, but
ig wrote:
>
>> From: Stefan Bodewig
>> Subject: Re: Feature request: ifbool/unlessbool
>> To: user@ant.apache.org
>> Date: Thursday, September 24, 2009, 5:27 AM
>> On 2009-09-24, Francis GALIEGUE
>>
>> wrote:
>>
>> > But ideally, I'd l
--- On Thu, 9/24/09, Stefan Bodewig wrote:
> From: Stefan Bodewig
> Subject: Re: Feature request: ifbool/unlessbool
> To: user@ant.apache.org
> Date: Thursday, September 24, 2009, 5:27 AM
> On 2009-09-24, Francis GALIEGUE
>
> wrote:
>
> > But ideally, I'
unless will pass if the property is either not set at all (current Ant
behavior) or is set and PropertyHelper expands it to Boolean.FALSE.
This sounds like an excellent solution!
Cheers,
Ernst
-
To unsubscribe, e-mail: user-
On 2009-09-24, Francis GALIEGUE wrote:
> But ideally, I'd like to use these properties all the time, with
> boolean values. Say, for example, if I have nomail set to 1 or true,
> then no mail is sent; if it's 0 or false, then the mail is sent. And
> the target would then read:
>
Ant 1.8.0[1] a
+1 to this feature request.
I am curious to know. why if and unless attributes in 'target' work the
way they do, i.e only check existence of the property and not its value.
Currently ant-contrib's if tag has to be used to accomplish this sort of
control over build execution.
-Prashant
On 9
