http://nagoya.apache.org/bugzilla/show_bug.cgi?id=984
*** shadow/984 Thu Mar 15 06:31:18 2001 --- shadow/984.tmp.17519 Thu Mar 15 06:46:20 2001 *************** *** 2,10 **** | Invalid DTD for tasks | +----------------------------------------------------------------------------+ | Bug #: 984 Product: Ant | ! | Status: NEW Version: 1.3 | ! | Resolution: Platform: PC | ! | Severity: Normal OS/Version: | | Priority: Low Component: Optional Tasks | +----------------------------------------------------------------------------+ | Assigned To: [EMAIL PROTECTED] | --- 2,10 ---- | Invalid DTD for tasks | +----------------------------------------------------------------------------+ | Bug #: 984 Product: Ant | ! | Status: RESOLVED Version: 1.3 | ! | Resolution: WONTFIX Platform: PC | ! | Severity: Normal OS/Version: All | | Priority: Low Component: Optional Tasks | +----------------------------------------------------------------------------+ | Assigned To: [EMAIL PROTECTED] | *************** *** 57,60 **** > but the docs do not specify these attributes. The test element requires a name ! attribute to run. Therefore I'd say the DTD is incorrect. --- 57,75 ---- > but the docs do not specify these attributes. The test element requires a name ! attribute to run. Therefore I'd say the DTD is incorrect. ! ! ------- Additional Comments From [EMAIL PROTECTED] 2001-03-15 06:46 ------- ! <junit> doesn't support a nested property element at all, you might mean ! <sysproperty>, but the DTD snippet is for the <property> task (and correct). ! ! As for <test>, well, a DTD is too limited to cover the full Ant syntax. The ! snippet you show is for the <test> task, not for <junit>'s child element. As ! a DTD has no way of saying "this is the DTD for a test element if it is a child ! of junit, in all other cases use that", there is nothing we can do when name ! collisions happen. ! ! We try to avoid them, but as you see, things happen. ! ! You could remove the test task from your CLASSPATH before running antstructure ! to get a better DTD.
