You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@ant.apache.org by bu...@apache.org on 2004/04/06 14:27:22 UTC

DO NOT REPLY [Bug 27735] - antstructure generates wrong dtd

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG 
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://issues.apache.org/bugzilla/show_bug.cgi?id=27735>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND 
INSERTED IN THE BUG DATABASE.

http://issues.apache.org/bugzilla/show_bug.cgi?id=27735

antstructure generates wrong dtd

bodewig@apache.org changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |dev@ant.apache.org
         AssignedTo|dev@ant.apache.org          |bodewig@apache.org



------- Additional Comments From bodewig@apache.org  2004-04-06 12:27 -------
Please see the FAQ, in particular the last bullet in
<http://ant.apache.org/faq.html#dtd>.

The manual should probably stress this a little more and I'll modify it shortly.

Ant's XML usage can not be correctly captured by a DTD.  There are two "different"
test elements (the deprecated task and the child of junit), two fail elements
(the task and the child of sound), two manifest elements (the task and the child
of jar).

The ELEMENT definition for attribute you get is the one of the nested child of
a different element, not manifest.  BTW, all elements have an id attribute in
Ant, it's just not very useful in most cases and omitted in the manual.

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@ant.apache.org
For additional commands, e-mail: dev-help@ant.apache.org