On Sun, 01 Jul 2007, Wascally Wabbit <[EMAIL PROTECTED]> wrote: > 2) To isolate and control a set of property and reference > modifications to a specific scope. Again this is within the scope of > any task container and is not limited to macrodefs. This compliments > the overlay function in that it captures undesired side-effects from > executing a reused set of tasks (macrodef, AntX various flow-control > tasksets, etc.) Additionally, the build script can pick-n-choose > which modifications it wants to let pass through to the project's > scope. [[The BIG point here is that isolate relies on the *SET* > functionality of PropertyHelper...it captures those sets to prevent > them from passing through to the parent project's property set.]]
This is a use-case I do understand, thanks. So we need to retain the ability to intercept the setter functionality. Stefan --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
