This Bugzilla instance is a read-only archive of historic NetBeans bug reports. To report a bug in NetBeans please follow the project's instructions for reporting issues.
The tag @link or @see in the javadoc should have import, but the annotation for unused imports does not look at it, so basically generation of javadoc gives warnings. To reproduce: 1. create class and add {@link ToSomeClass} in the javadoc. Note that ToSomeClass have to be class that is not used anywhere else, except the javadoc 2. build the javadoc, the warning will show: ToSomeClass.java:47: warning - Tag @see: reference not found: AnotherClass to solve the problem, add the import for the AnotherClass in the ToSomeClass, but than the bulb will appear that AnotherClass is not used... The bulb should look at the tags and watch the imports for the javadoc
Well, I would personally prefer to use the fully qualified name of the class in this case. As you said the tools for static code analysis do not consider javadoc as a valid reference to packages or classes, so adding an import for just making the javadoc tool happy causes this import to be reported as unused. IMO the solution is to show the hint bulb offering FQN for any unresolved references inside javadoc.
Yes, you are right that the better way is to use the fully qualified name of the class, but some solution for the users should be made. Maybe after Issue 37691, this problem will be gone. In my opinion your suggestion about bulb seems to be good one.
This should be implemented as part of the issue #122484. Use FQNs in NB 6.0. *** This issue has been marked as a duplicate of 122484 ***