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

Bug 362555

Summary:	workspace can not be used after upgrading EDT
Product:	z_Archived	Reporter:	Tony Chen <chenzhh>
Component:	EDT	Assignee:	Tony Chen <chenzhh>
Status:	CLOSED FIXED	QA Contact:
Severity:	major
Priority:	P1	CC:	smythew, svihovec
Version:	unspecified
Target Milestone:	---
Hardware:	PC
OS:	Windows XP
Whiteboard:

Description Tony Chen

2011-11-01 06:01:52 EDT

<input from Will>
It should not be a requirement for people to always start with a clean workspace after installing a new nightly build (this is both a technical statement and a statement about our philosophy). I understand new workspaces are required if fundamental changes are made to artifacts in the workspace (i.e. project nature IDs), but when the content of a project is still perfectly valid, developers should not have to scrap a workspace, start over, and manually copy artifacts over. Example: when we were closing down M3, I installed a M3 candidate build, which was only a few hours older than my current build and only included some IDE fixes, but when I started Eclipse using my old workbench, I could not get the VE to work (design/preview blank). I did a Clean (a few times), restarted the workbench at least once, etc - nothing worked. I had the same problem happen again yesterday, so I started digging into the .metadata directory, found a directory of index files (.metadata\.plugins\org.eclipse.edt.ide.core), deleted them, restarted the workbench, did a Clean, and everything worked. So, bottom line: think Clean should really clean the workspace (i.e. scrap cached index files, etc).

Comment 1 Brian Svihovec

2011-11-01 09:28:34 EDT

Before any changes are made for this defect, I would like to have a discussion about what is causing the problem and what is being proposed as a fix.

Comment 2 Tony Chen

2011-11-02 06:06:17 EDT

Will, 

I guess something caused an incorrect build state (or working copy build state). Some testers also mentioned this. 

I'm trying to recreate, but could not with M3 and latest nightly build. I wrote something with M3, then use the latest nightly build to open that workspace. Things just worked fine. If you have a workspace that run into this problem when open with the latest build, please attach that workspace so I can investigate.

Comment 3 Tony Chen

2011-11-08 03:01:13 EST

I could not recreate the problem now. (I believe I've saw this before). Now I can share workspace between M3, nightly build and my dev build without problem. It's possibly resolved indirectly by the fix to bug 363037. The problem fixed in bug 363037 can leads to all kinds of workspace invalid symptom.

I'll close the bug. If anyone run into this again, please reopen and attach the workspace.

Comment 4 Tony Chen

2011-11-10 22:03:45 EST

Tried various scenarios of sharing workspace, the problem does not happen again. Closing it.

Comment 5 Will Smythe

2011-11-10 22:21:19 EST

Sounds good.