Re: If and unless

, Tom Cleghorn wrote: > Hi, > > I'm puzzled by the new if and unless functionality - it seems that in > 1.9.2, the following, where ${id}.css *does* exist: > property="has.css.overrides"/> > > ...will set $has.css.overrides to 'true' as expected, b

If and unless

Hi, I'm puzzled by the new if and unless functionality - it seems that in 1.9.2, the following, where ${id}.css *does* exist: ...will set $has.css.overrides to 'true' as expected, but the property won't then evaluate as (boolean) true for this: Is this expected behavi

Re: I would like "echo" task to support the "if" and "unless" attribute

Francis Galiegue-4 wrote: > > Le Friday 19 December 2008 14:15:21 sactiw, vous avez écrit : >> Hi Guys, >>I really sometimes feel that task must should support >> the >> "if" and "unless" attribute. >> >>

Re: I would like "echo" task to support the "if" and "unless" attribute

Le Friday 19 December 2008 14:15:21 sactiw, vous avez écrit : > Hi Guys, >I really sometimes feel that task must should support the > "if" and "unless" attribute. > >So that I could write something like, > >This Pro

I would like "echo" task to support the "if" and "unless" attribute

Hi Guys, I really sometimes feel that task must should support the "if" and "unless" attribute. So that I could write something like, This Property Exists This Property Don't Exists I think this is a very useful

AW: Support mutliple if and unless

> Can ant support multiple if and unless. I would rather not need to use > ant-contrib for this. > > These will infact look for a property called "x,y": > Not directly. You would calculate a new property for that:

Support mutliple if and unless

Hi, Can ant support multiple if and unless. I would rather not need to use ant-contrib for this. These will infact look for a property called "x,y": Thanks - To unsubscribe, e-mail: [EMAIL PROTECTED] For additiona

Re: How to achieve "if" and "unless"-style behaviour with macrodefs?

You could probably define "if" and "unless" custom attributes in your macro and then use with ant-contrib's to check them inside of your macro. Something like this (untested!): ... other attributes...

How to achieve "if" and "unless"-style behaviour with macrodefs?

Hi, I have cases where it would be useful to call a macrodef if a property was set, but to skip it otherwise. If these were targets I could use the standard Ant if/unless attributes to achieve this behaviour, but macrodefs are called explicitly at certain points in the build file, rather than usi