Bug 161204 - code assist with unresolved types does not work when using 5.0 rt.jar
Summary: code assist with unresolved types does not work when using 5.0 rt.jar
Status: VERIFIED FIXED
Alias: None
Product: JDT
Classification: Eclipse Project
Component: Core (show other bugs)
Version: 3.3   Edit
Hardware: PC Windows XP
: P3 normal (vote)
Target Milestone: 3.3 M3   Edit
Assignee: David Audel CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2006-10-17 06:49 EDT by Dani Megert CLA
Modified: 2006-10-30 15:03 EST (History)
0 users

See Also:

Attachments
Proposed fix (37.16 KB, patch)
2006-10-19 09:40 EDT, David Audel CLA 		no flags Details | Diff
View All 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 2006-10-17 06:49:16 EDT 
JDT UI and JDT Core from HEAD (or I20061017-0800).

Have:
void foo() {
  HashMap m;
  m.<code assist>
}

==> you get proposals when the rt.jar is 1.4 but not when using 5.0.
Comment 1 David Audel CLA 2006-10-19 09:39:41 EDT 
Code assist filter possible types which will add compilation problems. But this filtering is too strict.
In this test case, java.util.HashMap will add a warning for a raw type.
Comment 2 David Audel CLA 2006-10-19 09:40:08 EDT 
Created attachment 52310 [details]
Proposed fix
Comment 3 David Audel CLA 2006-10-19 09:50:34 EDT 
Released for 3.3 M3.

Test added
  CompletionWithMissingTypesTests_1_5#test0012()

When the possible type could add a non optional problem there is no proposal.
When the possible type could add an optional problem, it is proposed but with a lesser relevance than if there is no problem.

As before, the behavior for problem of deprecation, visibility and access restriction is ruled by the corresponding code assist options.
Comment 4 Olivier Thomann CLA 2006-10-30 15:03:50 EST 
Verified for 3.3 M3 using warm-up build I20061030-0800