*** Issue 82237 has been marked as a duplicate of this issue. ***

Sounds cool; out of curiosity, is there a UI spec or wiki summary or anything
like that?

There is none AFAIK. As stated in summary field it is simply replacement of the
Autocomment tool.

I can summarize it here:

Javadoc fixes are intended to scan a source file for missing or corrupted
javadoc of class members and to offer editor hints to create missing javadoc or
to fix the corrupted javadoc. In order to preserve performance and not clutter
the editor stripe, just members with public and protected access are covered.
Later when there will be options for editor hints we could permit users to
customize the scope.

What is checked:
 - missing javadoc
 - @param tags if duplicate, missing, unknown
   - @param may stand for method/constructor parameter or class type parameter
   - jdk 5 and 6 implementation of javadoc ignores method type parameters
 - @throws/exception tags if duplicate, missing, unknown
 - @return tags if duplicate, missing, void
 - @deprecated tag if duplicate, missing (in case of @Deprecated annotation)
 - @inherited - explicit inheritance
 - implicit inheritance - check for super class javadoc
   - javadoc and its parts may be inherited

In case there are more then one missing javadoc then the Fix All Missing Javadoc
hint is offered together with each particular Create Missing Javadoc hint.

What is out of the scope of this task:
 - javadoc completion
 - import fixes
 - usage highlighting

What would be nice:
 - offer a Correct Javadoc hint in case of several javadoc hints on one class
member exist
 - generate javadoc on /** + Enter (issue #77039)

I have integrated the Javadoc fixes yesterday so you can try them. Since the
retouche still does not support javadoc modifications (#issue 90302) I had to
work around this and some cases like field groups are not supported yet (#issue
95359).

Cool, I will file issues blocking this as needed.

BTW:

Warning: in org.netbeans.modules.javadoc, not using spec.version.base, yet
declaring implementation dependencies; may lead to problems with Auto Update
(see http://wiki.netbeans.org/wiki/view/DevFaqImplementationDependency)

I guess if "Javadoc completion" and "import fixes" are out of scope, then so is
noting bad Javadoc links, e.g.

@see Objct#notify

FYI, I have added several options to limit number of hints as complaints against
the yellow editor have been rising :-) For more details see issue #95398.

Re Javadoc links
Yes, no links are checked now. But I would like to add it to nb 6.0. Likely it
has to go to the java/hints module to be consistent with import hints.

Re dependencies
fixed in
/cvs/javadoc/manifest.mf
new revision: 1.74; previous revision: 1.73
/cvs/javadoc/nbproject/project.properties
new revision: 1.8; previous revision: 1.7

Note that the help docs with 60 M9 still refer to the Autocomment Tool and how
to bring it up.  Should that be a new issue that blocks this one, or can that be
changed under this issue?

Help documentation is being reviewed before final release usually.

to pkeegan: Patrick is it necessary to file an issue for this?

Not totally necessary, particularly if it's covered in a visible place, such as
the New & Noteworthy pages.....

Should this already work in Build 200707240000, because it doesn't?

javadoc hints are disabled by default. See Tools/Options/Java Code/Hints.

*** Issue 158630 has been marked as a duplicate of this issue. ***