An opposite of availablelist, notavailablelist might be an idea as well. What I envision is something like <availablelist property=myapp.requirements classes=needed1,needed2,needed3 resources=needed5> <notavailablelist property=myapp.abort classes=abort1,abort2 file=abort3> <target ... if=myapp.requirements unless=myapp.abort ...>
Bear in mind the above are all or nothing. All the items are available or FALSE. All the items are not available or FALSE. i.e. one available item cause notavailablelist to set FALSE, one not available item cause availablelist to set FALSE ----- Original Message ----- From: "Stefan Bodewig" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Tuesday, May 23, 2000 9:08 AM Subject: Re: Call for patches > >>>>> "RB" == Ross Burton <[EMAIL PROTECTED]> writes: > > RB> I wanted Ant to be able to deal with multiple "if"s in the > RB> <target> block, > > I'm not convinced this is a good idea. If you open the box with this > ANDing of properties, others will need ORing and even more fancy > operations. > > Then, your patch is going to collide with the announced patch to add > an "unless" attribute to target by Brill Pappin. > > What would be the meaning of unless="prop1, prop2"? prop1 doesn't > exist OR prop2 doesn't exist (which would be the exact opposite of > your if) or neither prop1 nor prop2 exist? > > I see the need to change something with regard to the conditional > execution stuff but don't think adding boolean operations is the right > direction - although I cannot offer something better at the moment. > > Stefan >
