| AW: AW: Multiple IFs, or IFs on tasks | AW: AW: Multiple IFs, or IFs on tasks 2005-06-24 - By Jan.Materne@(protected)
I wouldnt use <antcall> for checking the properties - it creates a new project
instance
(I call that property-namespace :) and it?s difficult to return values.
Jan
>-----Urspr?ngliche Nachricht-----
>Von: Frank W. Zammetti [mailto:fzlists@(protected)]
>Gesendet: Freitag, 24. Juni 2005 15:32
>An: Ant Users List
>Cc: user@(protected)
>Betreff: Re: AW: Multiple IFs, or IFs on tasks
>
>Thank you Jan, that's a good approach too.
>
>FYI, I wound up taking a simple approach, after I thought
>about this some more... I simply have an antcall from one
>target to another that checks the second property. So it
>winds up being like a nested if in a sense...
>I would have to explain quite a bit to be able to explain why
>this worked in my case, but suffice it to say it does :)
>
>Thanks everyone, I appreciate all the suggestions!
>
>--
>Frank W. Zammetti
>Founder and Chief Software Architect
>Omnytex Technologies
>http://www.omnytex.com
>
>On Fri, June 24, 2005 1:04 am, Jan.Materne@(protected) said:
>> Common pattern:
>>
>>
>> <target name="do" depends="-do.check" if="do.condition">
>> <echo>All conditions set</echo>
>> </target>
>>
>> <target name="-do.check">
>> <condition property="do.condition">
>> ...
>> </condition>
>> </target>
>>
>>
>> Jan
>>
>>
>>>-----Urspr?ngliche Nachricht-----
>>>Von: Frank W. Zammetti [mailto:fzlists@(protected)]
>>>Gesendet: Donnerstag, 23. Juni 2005 17:42
>>>An: Ant Users List
>>>Cc: Ant Users List
>>>Betreff: Re: Multiple IFs, or IFs on tasks
>>>
>>>Ah, thank you Ninju! I wasn't aware of the <condition>
>task, I think
>>>that will do the trick. One extra step, but not a hassle.
>>>
>>>By the way, your name is only one letter off from ultimate coolness,
>>>but I'm sure you know that already :)
>>>
>>>--
>>>Frank W. Zammetti
>>>Founder and Chief Software Architect
>>>Omnytex Technologies
>>>http://www.omnytex.com
>>>
>>>On Thu, June 23, 2005 11:38 am, Ninju Bohra said:
>>>> Correct on both counts,
>>>>
>>>> For the first one, you may want to use a <condition> task to
>>>"consolidate"
>>>> all the individual flags into one property which you use
>in the if=""
>>>> attribute.
>>>>
>>>> As for the second, it is touch-and-go as to which tasks have an
>>>> if/unless attribute (i.e. some have them and some don't).
>The fail
>>>> task is one that comes to mind that has both but these
>>>attributes are
>>>> not "generic" to all tasks (there have numerous discussion on this
>>>> already, but to no avail :-(
>>>>
>>>> "Frank W. Zammetti" <fzlists@(protected)> wrote:
>>>> Hi all... I'm trying to solve a problem and one of the
>following two
>>>> approaches would work, and although it doesn't seem
>possible from my
>>>> testing, I wanted to run it by you guys...
>>>>
>>>> First, is it possible to do if checks on a target against multiple
>>>> properties? I tried simply have two if attributes, but
>that threw an
>>>> error, and I tried a comma-separated list within a single
>>>if, but that
>>>> resulted in the task not executing.
>>>>
>>>> Second, I might be missing it, but there doesn't seem to be an if
>>>> attribute on a task (like copy for instance), is that correct?
>>>>
>>>> Thanks all!
>>>>
>>>> --
>>>> Frank W. Zammetti
>>>> Founder and Chief Software Architect Omnytex Technologies
>>>> http://www.omnytex.com
>>>>
>>>>
>--------------------------------------------------------------------
>>>> - To unsubscribe, e-mail: user-unsubscribe@(protected) For
>>>additional
>>>> commands, e-mail: user-help@(protected)
>>>>
>>>>
>>>>
>>>>
>>>>
>>>> __________________________________________________
>>>> Do You Yahoo!?
>>>> Tired of spam? Yahoo! Mail has the best spam protection around
>>>> http://mail.yahoo.com
>>>
>>>
>>>---------------------------------------------------------------------
>>>To unsubscribe, e-mail: user-unsubscribe@(protected) For
>additional
>>>commands, e-mail: user-help@(protected)
>>>
>>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: user-unsubscribe@(protected) For
>additional
>> commands, e-mail: user-help@(protected)
>>
>>
>
>
>---------------------------------------------------------------------
>To unsubscribe, e-mail: user-unsubscribe@(protected) For
>additional commands, e-mail: user-help@(protected)
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: user-unsubscribe@(protected)
For additional commands, e-mail: user-help@(protected)
|
|
 |
