Bug 60571 - Javadoc-Warnings: Should not warn about 'invisible' references
Summary: Javadoc-Warnings: Should not warn about 'invisible' references
Status: RESOLVED DUPLICATE of bug 53977
Alias: None
Product: JDT
Classification: Eclipse Project
Component: Core (show other bugs)
Version: 3.0   Edit
Hardware: PC Windows XP
: P3 normal (vote)
Target Milestone: 3.1 M3   Edit
Assignee: Frederic Fusier CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2004-04-30 10:35 EDT by Martin Aeschlimann CLA
Modified: 2005-04-29 07:14 EDT (History)
0 users

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Martin Aeschlimann CLA 2004-04-30 10:35:55 EDT
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() {
	}
}
Comment 1 Olivier Thomann CLA 2004-04-30 10:41:35 EDT
You can set the level of visibility to check.
What did you set? private visibility?
Comment 2 Martin Aeschlimann CLA 2004-04-30 11:18:58 EDT
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)
Comment 3 Frederic Fusier CLA 2004-05-09 11:31:37 EDT
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...)
Comment 4 Frederic Fusier CLA 2004-05-09 11:50:48 EDT
Reopen to change resolve state...
Comment 5 Frederic Fusier CLA 2004-05-09 11:51:28 EDT

*** This bug has been marked as a duplicate of 53977 ***