I think we are streaching the meaning of <description> way beyond what is what defined for.
<description> is used by -projecthelp to generate online help on a terminal console. It was not conceived as a javados style facility. If we want to provide something like <xdoc> or <antdoc> to ducument ANT buildfiles, Then I think we should go for a diferent kind of element using the new facilityes that can allow retrieving XML fragments. Jose Alberto > -----Original Message----- > From: Claas Thiele [mailto:[EMAIL PROTECTED] > Sent: 29 April 2004 09:01 > To: Ant Developers List > Subject: Possible Enhancements to <description> datatype > > > Short: > a) description element should allow every attribute and every > markup inside. > b) description element should be usable inside macrodef, > presetdef and > any container task like sequential. > > a) und b) will not be processed by ant (simply ignored). text > nodes will > be processed only. > > What can be done with that things: > With this enhancements it is possible to add markup to description > elements related to a target documentation system or a > special ant doc > markup like javadoc has. > This seems to be necessary since macrodef makes reusable ant files > possible. Descriptions have to be more than a remark now. > The enhancements above make it possible to build a Automated > Documentation System for Ant like JavaDoc for Java. > > What do you think? > > > Claas > -- > ____________________________________________________________________ > Dipl.-Inf. Claas Thiele EMail: cthiele<at>ct42.de > Konradstr. 58 Web: http://ct42.de > 04315 Leipzig Tel.: +49 (0)341 68 70 92 29 > GERMANY Fax +49 (0)341 68 70 92 30 > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
