Bug 20751

Summary:	[F3] Discrepency between light bulbs and compiler
Product:	[Eclipse Project] JDT	Reporter:	Eric Nickell <nickell>
Component:	Core	Assignee:	Philipe Mulet <philippe_mulet>
Status:	RESOLVED WORKSFORME	QA Contact:
Severity:	normal
Priority:	P3	Keywords:	readme
Version:	2.0
Target Milestone:	2.1 M3
Hardware:	PC
OS:	Linux
Whiteboard:

Description Eric Nickell

2002-06-20 14:54:10 EDT

Okay, I admit it, I had some screwy code.  (Came as a result of poorly done
refactoring.)

I have Foo.java which has public class Foo, AND it also contains top-level
non-public class Xyzzy.  Bar.java in the same package contains public class Bar.
 There are references in class Bar to Xyzzy.  The compiler is happy with this,
but the editor keeps suggesting that we import the package in which both of
these modules are defined.  Nothing changes when clicking on the light bulb.

(I'm fixing my code so this problem goes away, but it should probably be doced
for 2.0 and fixed beyond so that the two pieces are in agreement.)

Comment 1 Dirk Baeumer

2002-07-30 11:00:13 EDT

Moving to core since they provide temporary problems.

Comment 2 Eric Nickell

2002-07-30 12:57:47 EDT

I have known people in organization to create problems, but I hadn't realized
that oti had a group *assigned* the responsibility of providing temporary
problems. 8-)

Comment 3 Philipe Mulet

2002-08-13 07:41:41 EDT

Could be scenario where UI did not refresh problems in editor (I've seen couple 
situations where this would occur, but haven't isolated steps to reproduce).

Comment 4 Philipe Mulet

2002-10-22 10:20:13 EDT

Closing, please reopen if scenario would still occur (with steps). We have 
addressed a few issues around this feature.