Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.

Bug 360436

Summary:	Project from CVS has egl file with annotated errors but no problem view errors
Product:	z_Archived	Reporter:	Kathy Carroll <carrollk>
Component:	EDT	Assignee:	Tony Chen <chenzhh>
Status:	CLOSED FIXED	QA Contact:
Severity:	normal
Priority:	P3	CC:	chenzhh, jspadea, pfyu
Version:	unspecified
Target Milestone:	---
Hardware:	PC
OS:	Windows XP
Whiteboard:

Description Kathy Carroll

2011-10-10 09:06:16 EDT

Using install build 201110090901.
Make sure you have the preference selected for Annotate errors as you type.
From kan-cvs-save.ottawa.ibm.com/cvsroot/rbd check out org.eclipse.edt.eunit.test.

Open file lang.expression.initializer.ObjectInitialization001.egl.  The editor will show numerous annotated errors but the problems view has none. Clean doesn't clear out anything.  Changing the egl Preference for annotate errors as you type cleans up the editor view.  Or if I copy the packages to a new project.

Comment 1 Justin Spadea

2011-10-10 10:30:20 EDT

Tony - The WCC is finding errors for some reason, but I did not debug into it. A good starting place is ProblemReconciler.java line 304 where the WCC gets invoked.

Comment 2 Tony Chen

2011-10-12 03:36:42 EDT

Kathy, I'm not able to recreate this. I checkout the project, wait for about 10 minutes until build is done, then open ObjectInitialization001, there's no error there. 

I have "annotate error as you type" enabled which is the default configuration.


Justin, can you recreate this?

Comment 3 Tony Chen

2011-10-12 03:53:30 EDT

PengFei helped retest this, he can recreate with build 201110090901, but can not with build 201110110900. 

Cathy, can you please verify it with the latest build, it's possibly fixed indirectly.

Comment 4 Justin Spadea

2011-10-12 09:11:06 EDT

I'm not seeing it anymore, but it did take me a couple attempts the other day to recreate it (didn't happen with my dev workspace, but did happen with a brand new one). It could be that it depends on a specific action to cause the problem (e.g. something loaded or not loaded causing it to happen). I think we should leave this open for a bit, see if it happens again in the next couple days.

Comment 5 Kathy Carroll

2011-10-17 17:43:03 EDT

I'm no longer seeing this issue.  You may resolve the bug.

Comment 6 Tony Chen

2011-10-24 05:14:56 EDT

Resolved since issue no longer appear in latest builds

Comment 7 Kathy Carroll

2011-10-25 11:58:34 EDT

verified with 201110241434 & closed