| Summary: | ISE in ContributedPartRenderer$2.setFocus | ||
|---|---|---|---|
| Product: | [Eclipse Project] Platform | Reporter: | Paul Webster <pwebster> |
| Component: | UI | Assignee: | Paul Webster <pwebster> |
| Status: | VERIFIED FIXED | QA Contact: | |
| Severity: | major | ||
| Priority: | P3 | CC: | curtis.windatt.public, daniel_megert, emoffatt, lneumeier, markus.kell.r, Mike_Wilson, pwebster, Udo.Walker |
| Version: | 4.3 | Flags: | Mike_Wilson:
pmc_approved+
emoffatt: review+ markus.kell.r: review+ |
| Target Milestone: | 4.3 RC4 | ||
| Hardware: | PC | ||
| OS: | Windows 7 | ||
| Whiteboard: | |||
| Bug Depends on: | 409324, 414048 | ||
| Bug Blocks: | |||
|
Description
Paul Webster
Fix for RC4: Remove the logging. We already have recursive protection code that works, and they views and editors behave correctly, so the risk of this change is minimal. This logging doesn't do more than fill up the logs. https://git.eclipse.org/r/13508 PW +1 for me for RC4. Dani, I need another component lead +1. Would you consider this for RC4? PW (In reply to comment #2) > +1 for me for RC4. Dani, I need another component lead +1. Would you > consider this for RC4? > > PW +1 to remove it for RC4. We already got the warning in other scenarios in 3.x and they did not help to find and fix the issues. If we bring it back in 4.4, then we should log more details, so that we can figure out what's happening. (In reply to comment #1) +1 for RC4. This looks like the safest fix at this point. The field "logger" is unused after this change, but the "@Optional" currently stops the compiler from issuing an error for that situation (bug 376590 comment 10). *** Bug 408810 has been marked as a duplicate of this bug. *** +1 A quick check shows that we don't get the ISE's anymore and I don't see any obvious regressions... Released as http://git.eclipse.org/c/platform/eclipse.platform.ui.git/commit/?id=e1f01e0fd4d84d6deff84135cad3d7387d72dcc6 PW Verified in I20130603-2000. NOTE: The bug number in the commit message is wrong (points to the 4.3.1 bug). *** Bug 415326 has been marked as a duplicate of this bug. *** |