Bug 225371 - Have to restart workbench to get rid of invalid compile errors
Summary: Have to restart workbench to get rid of invalid compile errors
Status: VERIFIED WORKSFORME
Alias: None
Product: JDT
Classification: Eclipse Project
Component: Core (show other bugs)
Version: 3.3.2   Edit
Hardware: PC Windows XP
: P3 normal with 1 vote (vote)
Target Milestone: 3.5 M2   Edit
Assignee: JDT-Core-Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2008-04-02 12:06 EDT by Pratik Shah CLA
Modified: 2008-09-15 09:24 EDT (History)
4 users (show)

See Also:

Attachments
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 Pratik Shah CLA 2008-04-02 12:06:17 EDT 
From time to time, my workspace gets in a state where I have tons of compile errors reported by JDT, even though there shouldn't be any.  Usually, this is when I first create a new workspace and checkout all the plug-in projects from the version control system, but it also happens sometimes when I have catch up with a lot of incoming structural changes.  No amount of cleaning and recompiling projects fixes this problem.  But if I restart the workbench, the compile errors go away.
Comment 1 Philipe Mulet CLA 2008-04-02 12:29:46 EDT 
Can you better describe the type of errors ? 
Of course steps to reproduce would help to find out what is going on.
Are you running 3.3.2 ?
Comment 2 Pratik Shah CLA 2008-04-02 12:58:17 EDT 
They're just compile errors.  By the hundreds, if not thousands.  usually, classes/plug-ins can't be found.

I've experienced this using 3.3 a few times and many people around me have as well.  I do know someone who ran into this with 3.4 today.

I have seen this many times, so I figured it must be a known JDT bug.  But I couldn't find anything like it when searching for it today, so I thought I'd open a bug report.  I'm surprised that you guys are not aware of this.  I suppose I should have reported it sooner.  I don't know how I can help you further, though, except to ping you next time I run into this problem.
Comment 3 Dani Megert CLA 2008-04-03 02:43:08 EDT 
This normally happens when PDE cache gets outdated. The build path is then also corrupted. I've also seen this but wasn't successful to come up with a reproducible test case.

Scenarios I've seen it is:
- after importing plug-ins over existing ones
- after loading plug-ins from CVS over existing ones
Comment 4 Jerome Lanneluc CLA 2008-04-07 08:40:28 EDT 
Do you have build path errors? To check if you have build path errors, go to the Problems view, click on the little triangle on the right and pull down the menu, then choose Group By > Java Problem type. If you have errors under the Build Path category, please paste them in this bug report.
Comment 5 Jerome Lanneluc CLA 2008-08-26 04:57:15 EDT 
Please reopen if you have the requested information.
Comment 6 Pratik Shah CLA 2008-08-26 16:26:58 EDT 
I haven't run into this problem lately, but if I do, I will paste the build path errors in here.
Comment 7 Frederic Fusier CLA 2008-09-15 09:24:01 EDT 
Verified for 3.5M2 using I20080914-2000.