Bugzilla – Full Text Bug Listing
| Summary: | Javadoc-Warnings: Should not warn about 'invisible' references | ||
|---|---|---|---|
| Product: | [Eclipse Project] JDT | Reporter: | Martin Aeschlimann <martinae> |
| Component: | Core | Assignee: | Frederic Fusier <frederic_fusier> |
| Status: | RESOLVED DUPLICATE | QA Contact: | |
| Severity: | normal | ||
| Priority: | P3 | ||
| Version: | 3.0 | ||
| Target Milestone: | 3.1 M3 | ||
| Hardware: | PC | ||
| OS: | Windows XP | ||
| Whiteboard: | |||
You can set the level of visibility to check. What did you set? private visibility? I had it 'as visible as protected' and the same setting in the Javadoc wizard. But I don't think that matters, this visibility relates on the commented member, not on the referenced member (a filter to decide for which members to create Javadoc) This works "as designed". We thought that is was a little poor to report only unbound references as Javadoc tool does. So, in this case, we just warns user he's refering to a non-visible method (typically sounds strange in Javaodc to refer to an "protected" method which should not be accessible nor documented...) Reopen to change resolve state... |
20040430 - Turn on checking of javadoc comments and tags - In the following code the method references have a warning 'foo is not visible'. When generating the doc, the Javadoc tool does not complain about this package pack; public class A { /** * Comment * @see pack2.B#foo() */ public void foo() { } } // ----------------- package pack2; /** * */ public class B { /** * Hello */ protected void foo() { } }