At Wednesday 5/1/2002 05:04 PM -0400, you wrote:
I've never seen anyone post any design or patches for integrating any kind
of templating into Ant's core. So currently it would need to be built on
top of Ant. I certainly welcome proposals and code patches that make it
more integrated - and can only comment on such after seeing it myself.
The first message I sent on this thread is in fact such a
design proposal. I really would welcome comments on it.
I've requoted it here FYI.
One constraining factor that I can think of is, how would you
deal with an "extends=" attribute which contains property
references?
=============================================================
From my brief perusal of Project.java, it looks like
this wouldn't be too hard to accomplish by adding
something like:
private Project template;
and then use this variable as a "last resort" for
obtaining properties/task/references definitions not
found in the "child" object.
The syntax might look something like:
<project name="r7" default="build" basedir="." extends="projtmpl.xml">
</project>
Is this an idea that has been broached before? Does it sound
like a good idea, bad idea? Any obvious complications I might be
overlooking?
=============================================================
--
To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
