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

Bug 219213

Summary:	silent completion failure
Product:	[Eclipse Project] JDT	Reporter:	Jeff McAffer <jeffmcaffer>
Component:	Core	Assignee:	David Audel <david_audel>
Status:	CLOSED WONTFIX	QA Contact:
Severity:	normal
Priority:	P3	CC:	jerome_lanneluc, martinae, remy.suen
Version:	3.4
Target Milestone:	---
Hardware:	PC
OS:	Windows Vista
Whiteboard:	stalebug

Description Jeff McAffer

2008-02-16 00:33:02 EST

in i0212

I have a target platform full of bundles, some with source, some without.  There is a particular class (IProfile) that if I reference from a class in my workspace and try to do code completion to get the methods, I get no proposals.  Other classes in the same bundle/package work fine.  

On investigation I found that IProfile extends IQuery which is in a different package from IProfile.  Further, my workspace class' bundle imports IProfile's package but not IQuery's.  In the past this sort of situation would have given a "class not found" error for IQuery.  That error is not appearing now and the code completion just does not work.

Comment 1 Jeff McAffer

2008-02-16 00:39:48 EST

more info.  I added the package import and completion now gives some results but only those methods that are directly defined on IProfile.  IQueryable's methods are not included in the completion proposal list.  More investigation reveals that IQueryable references a type (IProgressMonitor) that comes from still another package.

Again, some feedback here would be good.  In some cases I did get a compile error but in others there is nothing to help with the problem.

Comment 2 Jerome Lanneluc

2008-02-29 08:03:59 EST

Jeff, usually the reason of the completion failure is indicated in red on the status bar. Wasn't it simply not there? Or did you expect to get the feedback in another manner?

Comment 3 Eclipse Genie

2018-10-08 19:59:23 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.