Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 348538 - Code Completion not showing all matches
Summary: Code Completion not showing all matches
Status: CLOSED WONTFIX
Alias: None
Product: JDT
Classification: Eclipse Project
Component: Core (show other bugs)
Version: 3.7   Edit
Hardware: PC Windows 7
: P3 major (vote)
Target Milestone: ---   Edit
Assignee: Ayushman Jain CLA
QA Contact:
URL:
Whiteboard: stalebug
Keywords: needinfo
Depends on:
Blocks:
 
Reported: 2011-06-07 07:12 EDT by ChrisA CLA
Modified: 2019-11-23 06:55 EST (History)
1 user (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description ChrisA CLA 2011-06-07 07:12:50 EDT
Build Identifier: 20110218-0911

When running code completion for a large compilation unit (3600 files) will not code complete as previous versions did.  

eg.  I have a public class called ABCEventHistory (compiles, no errors)

in another class I type ABCE <+ctrl+space> and the dialogue box says 'No Default Proposals'.

Additionally if I type ABCEventHistory and then type <ctrl+shift+o> to organise imports I get '0 imports added'

But if I complete the import line by hand my class will compile without error.



Reproducible: Always

Steps to Reproduce:
1.Write class ABCEventHistory 
2.Write class ABCEventHistoryProcess 
3.In ABCEventHistoryProcess type ABCEv <+ctrl+space>
4.Line is not completed and dialogue box says 'No Default Proposals'
Comment 1 Ayushman Jain CLA 2011-06-07 09:53:05 EDT
I could not reproduce this. Chris, can you please provide a specific test case which clearly reproduces the issue? Maybe there's something there thats causing the problem.
Comment 2 Eclipse Genie CLA 2019-11-23 06:55:57 EST
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.