At the '99 JavaOne Javadoc Bird of a Feather, I held a survey of those
developers present what features they wanted (without offering any
features to them). This was suggested by Steve Lewis, who
has written Warnlet/Codelet doclets. After the group came up with their
list of features, I asked them to vote. This was voted the MOST HIGHLY
REQUESTED feature -- 56% of them wanted it.
Should be passed by TRC, since at one point they did not want the
tags to be extensible -- they considered the tags part of the language.
As the RFE is entered it is not clear what is being requested.
As a feature of the doclet API it doesn't make sense since timing
is unspecified. As a flag to the standard doclet, I am dubious
the someone would write this doclet code and no other code. Finally
as a architectural change in the standard doclet that makes customization
easier, it is probably a good idea, but certainly not a priority.
The doclet API doesn't do anything special with the tags. A doclet
can process whatever set of tags it wants. It seems that this is something
that would have to be done in the context of the standard doclet,
presumably by providing an API for clients to extend it, or by reorganizing
it to make it much easier to extend it by inheritance.
Am reassigning to Jamie. I think we should pass this by the TRC.
4359470 javadoc tool: Modify Comment.java for easy writing of custom tags
4039014 stddoclet: Tag listener-Flag misspelled tags while printing custom tags
4170018 stddoclet: Want ability to create simple custom tags without writing a
doclet (suggests @tag <newtag> <description>)
Perhaps a command line option such as
-customtag precondition "Pre-Condition"
that would honor @precondition as a tag and print out "Pre-Condition"
heading in the text.
Create a custom.tags file that lists custom tags and corresponding
This RFE has been implemented. Location of fix: