| Summary: | [Commands] NotDefinedException resetting perspective after update installation | ||
|---|---|---|---|
| Product: | [Eclipse Project] Platform | Reporter: | Andreas Goetz <cpuidle> |
| Component: | UI | Assignee: | Eric Moffatt <emoffatt> |
| Status: | RESOLVED DUPLICATE | QA Contact: | Eric Moffatt <emoffatt> |
| Severity: | normal | ||
| Priority: | P3 | CC: | Kevin_McGuire, mik.kersten, pascal, pwebster |
| Version: | 3.4 | ||
| Target Milestone: | --- | ||
| Hardware: | PC | ||
| OS: | Windows XP | ||
| Whiteboard: | |||
|
Description
Andreas Goetz
While its possible we broke restart with command changes, I'm more suspicious of the state we're left in post p2 update. If the application restarts fine, then it is not p2's fault. Since it means that the proper set of plug-ins is listed into the bundles.info. I'm questioning the dynamic ability of the workbench code. Still suspicious. I've done many restarts as part of testing accessibility (high contrast switch requires restart). Paul, thoughts? Eric, Paul says you've looked at bugs in this area recently. The issue here is that the user didn't restart - something is likely not reacting well to dynamic changes. (In reply to comment #5) > The issue here is that the user didn't restart - something is likely not > reacting well to dynamic changes. Ah thanks missed that in the initial description. There are still quite a few edge conditions that our current dynamic handling story doesn't handle. I doubt that we'll be able to cover them in 3.4... Moving to 3.5. This is an area where an overhaul of dynamics story would be good; we should come up with a viable strategy and then map -all- out extension point handling to it... Unfortunately the already beaten up P2 is going to get blamed for this. Bring it on! It is not like if we are not used to it now ;-) Move back to triage...This is another 'handle dynamic bundle changes more elegantly use case...I'll mark this one as a DUP of 218197. *** This bug has been marked as a duplicate of bug 218197 *** |