Bug 408095

Comment 1 Martin Oberhuber 2013-05-21 12:17:34 EDT

Cannot reproduce this with eclipse-classic-kepler-M7-win32 , nor with eclipse-SDK-4.3RC1-win32.

I can't imagine that the Eclipse EPP package contributes anything beyond the original Eclipse SDK which would trigger this.

Please try to reproduce with the original eclipse-SDK-4.3RC1 :
http://download.eclipse.org/eclipse/downloads/drops4/S-4.3RC1-201305162200/

If you can reproduce the case, reopen the bug and provide as exact steps.

Comment 2 Martin Oberhuber 2013-05-22 07:22:59 EDT

Created attachment 231298 [details]
Screenshots

Attached screenshots (sent by private E-Mail) illustrate the problem.

Compared to the original steps to reproduce, Screen4.png shows that the user had navigated to the Java online docs in the detached help window. Screen6.png and Screen8.png show several exceptions in the errorlog ("Unable to load resource file" and others).

Some exceptions point to remnants of WindowBuilder (org.eclipse.wb). It looks like the same workspace had been in use with the Eclipse Java package before. When opening the same workspace with Eclipse Classic/SDK later, some references to WindowBuilder are broken (actionset), because WindowBuilder is not part of Classic/SDK.

I assume that the unexpected switching from the Java perspective to the PDE perspective is due to one of the exceptions in the log. Please attach the log file such that we can see whether any further investigation makes sense. Also, please try to reproduce with Classic/SDK on a fresh empty workspace (I assume you won't be able to reproduce).

Thanks,
Martin

Comment 3 Martin Oberhuber 2013-05-22 07:44:26 EDT

You find the log as a file in the workspace (C:\workspace\.metadata\.log)

Or, in the errorlog view, press the “Export” button.

Or, Help > About > Installations Details : Configuration Tab : View Errorlog button , then save.

Comment 4 Martin Oberhuber 2013-05-22 16:26:53 EDT

I reproduced the problem with Eclipse Platform SDK 4.3M7.
I could not reproduce it with Eclipse 4.3RC1.

I assume that the problem has been fixed for RC1 - reassigning to Platform / UI for duplicating to the proper bug fix.

Steps to reproduce with Platform SDK 4.3M7:
-------------------------------------------
1. Launch SDK on a fresh empty workspace
2. In Welcome page, choose SWT Examples and have them installed
3. New > Other > Code Samples > SWT
4. Open "Plug-In Development" perspective
5. Open "Debug" perspective
6. Close "Java" Perspective
7. Switch to "Plug In Development" perspective, close the Welcome view
8. Expan o.e.swt.examples.paint, dbl click PainView to load in the editor
9. Select "ViewPart", F1 open context help
10. Drag Context Help View out of the IDE to make a separate window
11. In the detached help window navigate to "IViewPart" then to "IWorkbenchPart"
12. Quite Eclipse and restart --> Help View reappears detached, 
    PDE perspective is still active
13. Close detached help window
14. Quit and restart Workbench
--> Workbench comes up in the default "Java" perspective, perspective layout
    is all destroyed
--> Errorlog view has attached, this is the key exception:


!MESSAGE Unable to load resource file:/D:/Eclipse/eclipse4.3m7/workspace/.metadata/.plugins/org.eclipse.e4.workbench/workbench.xmi
!STACK 0
org.eclipse.emf.ecore.resource.impl.ResourceSetImpl$1DiagnosticWrappedException: org.eclipse.emf.ecore.xmi.IllegalValueException: Value 'org.eclipse.e4.ui.model.application.ui.basic.impl.PartStackImpl@83020 (elementId: stickyFolderRight, tags: null, contributorURI: null) (widget: null, renderer: null, toBeRendered: false, onTop: false, visible: true, containerData: 2500, accessibilityPhrase: null)' is not legal. (file:/D:/Eclipse/eclipse4.3m7/workspace/.metadata/.plugins/org.eclipse.e4.workbench/workbench.xmi, -1, -1)
	at org.eclipse.emf.ecore.resource.impl.ResourceSetImpl.handleDemandLoadException(ResourceSetImpl.java:319)

Comment 5 Martin Oberhuber 2013-05-22 16:27:57 EDT

Created attachment 231333 [details]
Workbench log

Comment 6 Dani Megert 2013-05-23 06:49:39 EDT

*** This bug has been marked as a duplicate of bug 407288 ***