Bug 219235

Summary:	stale state
Product:	[Eclipse Project] JDT	Reporter:	Jeff McAffer <jeffmcaffer>
Component:	Core	Assignee:	JDT-Core-Inbox <jdt-core-inbox>
Status:	VERIFIED WORKSFORME	QA Contact:
Severity:	normal
Priority:	P3	CC:	remy.suen
Version:	3.4	Keywords:	needinfo
Target Milestone:	3.5 M2
Hardware:	PC
OS:	Windows Vista
Whiteboard:

Description Jeff McAffer

2008-02-16 13:00:44 EST

in i02012

This report is somewhat vague but I wanted to capture my experience in case others are seeing the same thing.

In a few cases while developing some code it appears that the JDT state was getting stale for particular classes.  For example, I had some code that threw and exception so the following code was marked as unreachable.  Makes sense.  I removed the exceptoin and saved but the error remained.  I had to do other changes in the code and save again to get the errors to go away.

I had a similar problem when I had a problem (don't remember what it was), I fixed it but the error did not go away until I fixed another error (adding a try/catch block).  It was quite confusing because I fixed the first problem and saved but the error did not go away.

Since this all happened in the normal flow of development I do not have easy steps to reproduce.  Treat this as one data point...

Comment 1 Jerome Lanneluc

2008-03-19 11:16:31 EDT

Unfortunately there is not much we can do here without that little information. Do you still have the code you made reference to in the sentence: "the following code was marked as unreachable"?

Comment 2 Jerome Lanneluc

2008-08-26 07:41:28 EDT

Not enough information. Please reopen if you have more details

Comment 3 Frederic Fusier

2008-09-15 09:17:27 EDT

Verified for 3.5M2 using I20080914-2000.