--- Geoff Meakin <[EMAIL PROTECTED]> wrote:
> As far as I know, you can then set properties which they haven't
> set automatically using something like
> <condition property="p1" value="p2">
> <equals arg1="${p1}" arg2="$${p1}"/>
> </condition>
>
> or the <not><isset></not> nested task, which certainly works
> in 1.4.1 (I havent tried it on 1.5b1). I have a similar
> situation to what I think you're describing, and that's what
> I do.
Just a note: There's no need to test whether a property's been set before
assigning a default value to it, since properties are (for the most part)
immutable (ie., only those properties that haven't been set by the user
will end up with the default values).
Diane
=====
([EMAIL PROTECTED])
__________________________________________________
Do You Yahoo!?
LAUNCH - Your Yahoo! Music Experience
http://launch.yahoo.com
--
To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
