Re: Using available's property setting ability inside a condition, is it possible?

2002-11-11 Thread Stefan Bodewig
On 11 Nov 2002, David Budworth <[EMAIL PROTECTED]> wrote: > Actually, this is what I tried from the start But you get a > deprecation warning about using available to overwrite an existing > property OK, so instead of >> > property="compiler.type" value="jikes"/> >> > property="com

Re: Using available's property setting ability inside a condition,is it possible?

2002-11-11 Thread David Budworth
Actually, this is what I tried from the start But you get a deprecation warning about using available to overwrite an existing property I ended up doing what's below. Looking at it now though, I'm not sure why ${found.compiler} doesn't get overwritten with javac after it's found jikes (both are i

Re: Using available's property setting ability inside a condition, is it possible?

2002-11-11 Thread Stefan Bodewig
On 09 Nov 2002, David Budworth <[EMAIL PROTECTED]> wrote: > The only workaround for this I can find is to do it the old way, of > multiple targets with an "unless=compiler.type" tag on them. So I'll try to help to find another one: Compiler found: ${compiler.found}, type: ${co