Re: Variable number of parameters for a task

2006-01-16 Thread Stefan Bodewig
On Mon, 16 Jan 2006, Michael <[EMAIL PROTECTED]> wrote: > Maybe I can use conditionals to set a property to null (which would > be ok) if it is not set (Is there a way to set a property to > null?!)? No, but will an empty string work as well? If so, just use to set it. If the property has been

Re: Variable number of parameters for a task

2006-01-16 Thread Petar Tahchiev
On 16/01/06, Michael Böckling <[EMAIL PROTECTED]> wrote: > > Hi, > > I have a situation where I don't know whether or not a property is set > at runtime. > As we all know, if a property is not set, its literal value is passed. > > Example: > > > I don't know beforehand if ${var2} is set at runtime

Variable number of parameters for a task

2006-01-16 Thread Michael Böckling
Hi, I have a situation where I don't know whether or not a property is set at runtime. As we all know, if a property is not set, its literal value is passed. Example: I don't know beforehand if ${var2} is set at runtime or not, so sometimes the literal "${var2}" is passed to the task, which