Summary: | View errors when launching with out the plugins needed to create them | ||
---|---|---|---|
Product: | [Eclipse Project] Platform | Reporter: | Peter Manahan <manahan> |
Component: | UI | Assignee: | Eduardo Pereira <eduardo_pereira> |
Status: | RESOLVED FIXED | QA Contact: | |
Severity: | major | ||
Priority: | P1 | CC: | eduardo_pereira, greg_adams |
Version: | 2.0 | ||
Target Milestone: | 2.0.1 | ||
Hardware: | PC | ||
OS: | All | ||
Whiteboard: |
Description
Peter Manahan
2002-05-03 15:24:33 EDT
Using integration build 502 you can use the update manager and the base eclipse to see the behaviour described in 2 above. 1.Launch eclipse open several perspectives JDT and PDE based ones. 2. Open the update manager perspective. An expand current configuration until you see the JDT and PDE feaures. 3. Select the PDE and Unconfigure. Hit cancel on the question to restart 4. Select the JDT and Unconfigure. 5. If you restart now Eclipse restarts itself but comes up with no errors as it is in the Install/Update perspective. Switch to the previously opened JDT and PDE perspectives and in you'll begin to get several error dialogs. When migrating from Eclipse 1.0 to 2.0, we now delete the workbench.xml (with warning, and opportunity to cancel), forcing a clean slate in the UI. However, the update scenario you outline is still problematic. We should try to handle these errors better, or at least collect them and present a single dialog. We also have a dependency on this being fixed. As a general statement all extension points need to be behave properly under uninstall (John K. claimed this was the case already?). Needed for 2.0.1. Change restoreState to return IStatus (MultiStatu) and collected them in a single dialog. Released in the HEAD stream. Released in the 201 stream as well. Fix released in both streams (201 and HEAD). All errors are collected in one single dialog. |