| Summary: | [plan] Serviceability | ||
|---|---|---|---|
| Product: | [Eclipse Project] Platform | Reporter: | DJ Houghton <dj.houghton> |
| Component: | UI | Assignee: | Tod Creasey <Tod_Creasey> |
| Status: | VERIFIED FIXED | QA Contact: | |
| Severity: | enhancement | ||
| Priority: | P4 | CC: | bokowski, bpasero, bradleyjames, celek, eclipse, equinox.framework-inbox, jacek.pospychala, jeffmcaffer, Konstantin.Scheglov, Michael_Rennie, mik.kersten, mober.at+eclipse, pnehrer, Szymon.Brandys |
| Version: | 3.3 | Keywords: | plan |
| Target Milestone: | 3.4 | ||
| Hardware: | All | ||
| OS: | All | ||
| Whiteboard: | |||
| Bug Depends on: | 144035, 202044 | ||
| Bug Blocks: | |||
|
Description
DJ Houghton
Is there a more concrete background information on this item? Is it about logging, or end-user error reporting, or something else? Szymon could you add a list of the resources for servicability to this bug please? Bug 144035 ("collect and aggregate automated error reports") seems to be one work item for this, and Mylyn already seems to have some solutions as per Bug 144035 comment 4. Plugins should be able to register as "log providers", such that at the time an error report is generated, the failing component can provide additional logs it may have collected for the report. At the time the error report is generated for a failing component, users could also be prompted with a screen to enable additional logging / tracing options, such that even more information is collected when they try to reproduce the same issue right away. Those are useful links http://wiki.eclipse.org/Platform_UI_Error_Handling http://wiki.eclipse.org/Status_Handling_Best_Practices Marking FIXED as our feature freeze is done. Marking verified |