Bug 400435 - Inside Javadoc of an interface: methods from 'Object' treated as visible
Summary: Inside Javadoc of an interface: methods from 'Object' treated as visible
Status: NEW
Alias: None
Product: JDT
Classification: Eclipse Project
Component: Core (show other bugs)
Version: 4.3   Edit
Hardware: PC Windows 7
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: JDT-Core-Inbox CLA
QA Contact:
URL:
Whiteboard: stalebug
Keywords:
Depends on:
Blocks:
 
Reported: 2013-02-11 06:46 EST by Dani Megert CLA
Modified: 2022-10-02 15:28 EDT (History)
0 users

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Dani Megert CLA 2013-02-11 06:46:04 EST 
4.3 M5a.

Inside Javadoc of an interface: methods from 'Object' treated as visible. Probably introduced with bug 191322.


Test Case 1:

package p;

/**
 * #<code assist>
 */
public interface I {

}
==> wrongly suggest methods from 'Object'


Test Case 2:
	package p;
	
	/**
	 * {@link #equals(Object)}
	 */
	public interface I {
	
	}

No error is shown after enabling Javadoc validation for non visible references. Generating Javadoc for that interface will issue a warning that #equals is not found.
Comment 1 Eclipse Genie CLA 2020-08-05 20:25:17 EDT 
This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet.

If you have further information on the current state of the bug, please add it. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant.

--
The automated Eclipse Genie.
Comment 2 Eclipse Genie CLA 2022-10-02 15:28:51 EDT 
This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet.

If you have further information on the current state of the bug, please add it. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant.

--
The automated Eclipse Genie.