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

Bug 404659

Summary: [Migrate]Eclipse 4.2 can't keep the latest perspective of old workspace which created on eclipse 3.6
Product: [Eclipse Project] Platform Reporter: Peng Wang <birdstar>
Component: IDEAssignee: Platform UI Triaged <platform-ui-triaged>
Status: CLOSED WONTFIX QA Contact:
Severity: normal    
Priority: P3 CC: riwagner
Version: 4.2Keywords: helpwanted
Target Milestone: ---   
Hardware: PC   
OS: Windows 7   
Whiteboard: stalebug

Description Peng Wang CLA 2013-04-01 06:11:16 EDT
I use eclipse v4.2 to open a old workspace which created on eclipse v3.6. Could not keep the latest perspective as use v3.6 open it. Seems v4.2 could not read the v3.6 workspace store file,that is a migrate issue.
Comment 1 Paul Webster CLA 2013-04-02 08:18:13 EDT
Yes, when migrating to a new eclipse, UI state can be disgarded: http://www.eclipse.org/projects/project-plan.php?projectid=eclipse#compatibility

But if someone would like to try migrating the .metadata/.plugins/org.eclipse.ui.workbench/workbench.xml to the model that's loaded up we accept patches. 

PW
Comment 2 Richard Wagner CLA 2015-02-24 18:11:21 EST
I'm a newly registered user of this bug DB, so I hope it's OK for me to ask questions here, given they're related to this ticket.

My employer has an v3.8-based, RCP-based "Desktop" product where end-users create their own custom perspectives as a matter of course.  That is, unlike Eclipse itself which has a fixed set of extension-defined perspectives (perspective customization aside), our "Desktop" product essentially has no fixed perspective: just a (mostly) initially empty one which end-users add views to, with those modified perspectives then saved to the workspace using (internally) the perspective "Save As..." functionality.

So we want to upgrade the Eclipse code-base to v4.x, but this problem is severe for us.  We have many end-users, and they have MANY 3.8-created workspaces deployed in their systems, and it's simply unacceptable for us to release a v4.x-based version of the Desktop, for end-users to find that there workspace/perspective/custom-"dashboard" definitions are simply gone.

So I've been working on code the detects the use-case where a v4.x-based Desktop is used to open a workspace last created/opened via our v3.8 Desktop, and (transparent to the user) the 3.8 "workbench.xml" data is read at startup and used to dynamically populate a functionally equivalent E4 Application Model.

As someone new to E4, it's been a challenge, to say the least.

So really my question is:  I am right in thinking that I should NOT wait and hope - at all - for the Platform UI team and "eclipse.org" to release an update that includes similar, transparent conversion of 3.8 (or earlier) workspaces?

This is an open ticket, but it has no "Target Milestone" or individual Assignee, so that implies to me that I should continue implementing our own solution.  Do you agree?

Thanks, Rich
Comment 3 Eclipse Genie CLA 2020-06-12 03:03:20 EDT
This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet. As such, we're closing this bug.

If you have further information on the current state of the bug, please add it and reopen this bug. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant.

--
The automated Eclipse Genie.