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.
Summary: | javadoc @link tag and unused imports | ||
---|---|---|---|
Product: | java | Reporter: | migi <migi> |
Component: | Javadoc | Assignee: | issues@editor <issues> |
Status: | RESOLVED DUPLICATE | ||
Severity: | blocker | ||
Priority: | P4 | ||
Version: | 6.x | ||
Hardware: | Sun | ||
OS: | All | ||
Issue Type: | DEFECT | Exception Reporter: |
Description
migi
2007-04-12 14:08:58 UTC
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 *** |