DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT <http://nagoya.apache.org/bugzilla/show_bug.cgi?id=23737>. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE.
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=23737 javadoc tag order Summary: javadoc tag order Product: Ant Version: 1.5.4 Platform: All OS/Version: All Status: NEW Severity: Enhancement Priority: Other Component: Core tasks AssignedTo: [EMAIL PROTECTED] ReportedBy: [EMAIL PROTECTED] Generating javadoc projects I use a bundle of custom tags, preferring a mixed sort order of standard and custom tags by repeating the standard ones in the list of "-tag" options (following the hint in the JDK javadoc manual: "Order of tags"), e. g.: -tag customtag_A:a:"A:" -tag version -tag customtag_B:t:"B:" -tag customtag_C:a:"C:" -tag since ... (and so on) Migrating from scripts to ant, this technique can't be used with the <javadoc><tag> node, because I have to specify a "description" attribute, marking the entry as a custom tag. My workaround is to place all of the "-tag" options within the "additionalparam" attribute of the <tag> node. I would like to suggest a solution where standard tags can appear within the list of <tag> entries with a new attribute like: "type=[custom|standard]" [defaults to 'custom'!] or "standard" [defaults to 'false'!], so that the standard tags can be repeated and the doc's tag order will correspond to the order of the list of <javadoc><tag> nodes in the ant build file, e. g.: <javadoc> ... <tag name="customtag_A" description="A:"/> <tag name="version" type="standard"/> <tag name="customtag_B" description="B:"/> <tag name="customtag_C" description="C:"/> <tag name="since" type="standard"/> ... --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
