ant-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From bugzi...@apache.org
Subject DO NOT REPLY [Bug 28446] New: - Annotation or documentation nodes
Date Sat, 17 Apr 2004 02:38:01 GMT
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=28446>.
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=28446

Annotation or documentation nodes

           Summary: Annotation or documentation nodes
           Product: Ant
           Version: 1.6.1
          Platform: All
        OS/Version: All
            Status: NEW
          Severity: Enhancement
          Priority: Other
         Component: Core
        AssignedTo: dev@ant.apache.org
        ReportedBy: mharrah@dollartree.com


We like to use XSLT over our build files to generate documentation of our 
build scripts.  Currently we have defined a macrodef called documentation that 
takes a type attribute (such as "usage", "example", "introduction", etc.) and 
a content attribute ("text" or "html"), but doesn't do anything at all.  We 
then use the macro in various places to document what we are doing.

However, to use this inside a macrodef, we have to put it inside the 
sequential section instead of in the macrodef header.

It would be nice if there were a built-in ability to put in a <documentation 
type="foo" content="bar"> type of construct anywhere in your build script.  
This would allow tools to get documentation of the script without having to 
parse XML comments.

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


Mime
View raw message