references. A
> solution using this approach might be to make ResourceDecorator
> concrete, add a resource property setter for XML attribute
> accessibility, redefine a ResourceDecorator to, by ...
No, then I'd rather see a "parsed" resource 8-)
Stefan
ry Objects,
that such a resolved property ought to transparently behave as the
parsed Resource, including name and all other properties. I will
code this ASAP and commit when I finish or after 1.8.0 is released,
whichever is later. While I do think this behavior is a reasonable
expectation
Hi,
Stefan Bodewig wrote:
On 2010-01-28, Matt Benson wrote:
Okay, using custom PropertyEvaluators (e.g. the "types" evaluator from
the props antlib) we can set an attribute of a task or type to an
arbitrary Ant type. I would like to (after 1.8.0, I suppose) add a
resource implementati
On 2010-01-28, Matt Benson wrote:
> Okay, using custom PropertyEvaluators (e.g. the "types" evaluator from
> the props antlib) we can set an attribute of a task or type to an
> arbitrary Ant type. I would like to (after 1.8.0, I suppose) add a
> resource implementation that simply allows one t
Okay, using custom PropertyEvaluators (e.g. the "types" evaluator
from the props antlib) we can set an attribute of a task or type to
an arbitrary Ant type. I would like to (after 1.8.0, I suppose) add
a resource implementation that simply allows one to say, e.g.:
Now, programmatically,
