Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.

Bug 384559

Summary:	Open declaration (F3) doesn't work when a specific import is present
Product:	[Eclipse Project] JDT	Reporter:	Alain Picard <picard>
Component:	Core	Assignee:	Ayushman Jain <amj87.iitr>
Status:	CLOSED WONTFIX	QA Contact:
Severity:	normal
Priority:	P3	CC:	amj87.iitr
Version:	3.7
Target Milestone:	---
Hardware:	PC
OS:	Windows 7
Whiteboard:	stalebug

Description Alain Picard

2012-07-08 20:53:09 EDT

Build Identifier: I20120608-1200

I have a very weird situation where it seems that class that import a specific interface their "Open Declaration" stops working and you get a beep with the following message at the bottom of the screen:
"Current text selection cannot be opened in an editor"

I was able to remove it from one class and everything started working (removing the reference but leaving the import in place would not fix it.

I have another class that needs the import and it doesn't work.

OTOH, the class that actually implements this interface has the import but doesn't show the problem.

If it matters the interface name is: org.eclipse.emf.cdo.server.hgdb.IHgDbStoreAccessor

Reproducible: Always

Steps to Reproduce:
1. Use the above referenced interface in your class code
2. Import the interface
3. get the error.

One more point to note:
If I use a wildcard for the import, it doesn't change anything. If I remove the import the issues goes away (but obviously errors appear in my code).

Comment 1 Ayushman Jain

2012-07-09 02:10:30 EDT

Can you please provide a reproducible test case? Thanks in advance!

Comment 2 Eclipse Genie

2019-09-17 13:43:35 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.