ant-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Jan.Mate...@rzf.fin-nrw.de
Subject RE: Target executes despite 'unless'
Date Mon, 01 Sep 2003 05:40:19 GMT
Do a 
    <echo>$${was.inited} = ${was.inited}</echo>
at the begin of your init target and you can see the value.
If a 
    ${was.inited}
is written, that property is not set.


Jan

> -----Original Message-----
> From: Jack J. Woehr [mailto:jax@purematrix.com]
> Sent: Friday, August 29, 2003 10:57 PM
> To: Ant Users List
> Subject: Re: Target executes despite 'unless'
> 
> 
> Dominique Devienne wrote:
> 
> > Depends on the 'was.inited' property existence, not 
> value... This is a usual
> > trap. Test the value using <condition <istrue>>, in another target
> > unfortunately. --DD
> >
> 
> Well, I've looked at this more and it works okay in a small 
> example. In my real
> build file, I've got lots of ant and antcall tasks but none 
> set inheritAll so they should
> be by default inhering that "was.inited" property okay, right?
> 
> 
> --
> Jack J. Woehr      # You measure democracy by the freedom it
> Senior Consultant  # gives its dissidents, not the freedom
> Purematrix, Inc.   # it gives its assimilated conformists.
> www.purematrix.com #         - Abbie Hoffman
> 
> 
> 
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: user-unsubscribe@ant.apache.org
> For additional commands, e-mail: user-help@ant.apache.org
> 

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message