ant-user mailing list archives

Condor wrote:
> The reason you can't easily have a DTD for Ant, in general, is not to do
> with attribute values and more to do with the fact that the document
> itself can modify the allowable elements (i.e. taskdef can create new
> elements).
I am not sure how to solve all of the problems associated with creating a
DTD for ant, but it seems to me that this one could be solved (in Ant2) if
we were to have a separate XML document for configuring Ant's environment.
The Taskdefs would go in this configuration document and not in the
build.xml. Perhaps others do not have this perception, but I've always
thought that the taskdefs, etc. were really metadata that didn't belong in
the build.xml anyway.
Once this were done this second file could be consulted for building the
DTD. Perhaps we'd also need a contract for custom tasks that would require
them to identify themselves in such a way that accurate DTD info could be
built. This mechanism might also help on the documentation side as well.
I do think that being able to produce a validatable build.xml is a worthy
goal, though it will certianly require some thought.
John-Mason Shackelford
Software Developer
NCS Pearson - Measurement Services
2510 North Dodge St.
Iowa City, IA 52245
319-354-9200x6214
shacjo@ncs.com
****************************************************************************
This email may contain confidential material.
If you were not an intended recipient,
Please notify the sender and delete all copies.
We may monitor email to and from our network.
****************************************************************************
--
To unsubscribe, e-mail: <mailto:ant-user-unsubscribe@jakarta.apache.org>
For additional commands, e-mail: <mailto:ant-user-help@jakarta.apache.org>