Well, if you use Ant-Contrib's var and side-step property immutability
altogether the problem is moot then, no? In any case, there's no need
for entities. Easier on the eye to simply use an explicit prefix. Of
course one runs the risk of overriding an existing 'real'
property, but any prefix speci
Improved version (using ant-contrib). I suppose we'll have to wait for
ANT 1.7 in order to have a 100% solution for scoped variables.
build.xml :
]>
&test-uid;.test : ${&test-uid;.test}
macrodef.xml:
]>
¯odef1-uid;.test :
I don't see how this really helps, I'm sorry ;-)
The problem is when you invoke *several times* a macrodef that uses
internally. You would need to use a different prefix (that
what your entity is equivalent to) for the different runs of the same
macro to use different property names.
Which is wh
