EVALUATION
A doc checker doclet should be written.
robert.field@Eng 1997-12-08
Alan, is this something you can add to your docchecker doclet?
Perhaps provide a file listing all valid tags against which you
can check.
doug.kramer@Eng 1998-04-03
Reassigning to Eric, since he's now working on DocCheck doclet.
doug.kramer@Eng 1998-07-29
Although DocChecker could parse the text of the comment to identify
such errors, it would be redoing work that JavaDoc is already doing.
JavaDoc's recognizer should see * then @ and if it then does not
see a recognized keyword, it should generate an error.
Reassigning to the JavaDoc team, by way of Doug. (Possibly Atul should
get it?)
eric.armstrong@eng 1998-08-17
Making this change would require that the developer create a list of
valid tags that javadoc inspects, since we now allow developers to make
up their own custom tags. Changing to P5, since this won't happen
this release.
doug.kramer@eng 1998-08-17
I am combining this request with that of allowing the printing custom tags
through a tag listener, as suggested at Javadoc BOF at JavaOne '99.
doug.kramer@Eng 1999-09-21
I am reassigning to jamieh@eng because this does not require any tool or
API support.
neal.gafter@Eng 2001-02-27
Request #1, emitting a warning for misspellings, is something Jamie can do
now that he has implemented custom tags (which was request #2).
doug.kramer@Eng 2001-06-28
This RFE has been implemented. Location of fix:
CustomTagFactory.java
AbstractSubWriter.java
ConstructorSubWriter.java
HtmlStandardWriter.java
MethodSubWriter.java
standard.properties
jamie.ho@Eng 2001-07-06
|