Bug 161204

Summary:

code assist with unresolved types does not work when using 5.0 rt.jar

Product:

[Eclipse Project] JDT

Reporter:

Dani Megert <daniel_megert>

Component:

Core

Assignee:

David Audel <david_audel>

Status:

VERIFIED FIXED

QA Contact:

Severity:

normal

Priority:

Version:

3.3

Target Milestone:

3.3 M3

Hardware:

OS:

Windows XP

Whiteboard:

Attachments:

Description	Flags
Proposed fix	none

Description Dani Megert

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

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

2006-10-19 09:40:08 EDT

Created attachment 52310 [details]
Proposed fix

Comment 3 David Audel

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

2006-10-30 15:03:50 EST

Verified for 3.3 M3 using warm-up build I20061030-0800