ant-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Wascally Wabbit <wascallywab...@earthling.net>
Subject RE: Target or macrodef?
Date Wed, 25 Aug 2004 20:56:48 GMT
At 03:29 PM 8/25/2004, you wrote:
>Variables and your proposal below are not a solution for tasks that set
>properties, e.g. exec, loadfile, etc. You need to surround the macro
>body with scoping tags or maybe just add an option to the sequential
>tag. Something like
>
>    <macrodef name="mymacro">
>       ...
>       <sequential>
>          <localscope>
>             ...
>          </localscope>
>       </sequential>
>    </macrodef>
>
>Or
>
>    <macrodef name="mymacro">
>       ...
>       <sequential localscope="true">
>          ...
>       </sequential>
>    </macrodef>


To see what this might entail, try the <isolate> and <overlay>
tasksets in the AntXtras ant extension. They let you do something
like the approach above:

         <macrodef name="blablabla">
           ...
          <isolate>
             touch-touch-touch...
          </isolate>
        </macrodef>

Any ant properties touched inside the <isolate> are not seen
once that element exists.



The Wabbit 



---------------------------------------------------------------------
To unsubscribe, e-mail: user-unsubscribe@ant.apache.org
For additional commands, e-mail: user-help@ant.apache.org


Mime
View raw message