Bugzilla – Full Text Bug Listing
| Summary: | Build Error info not accessible (1GDUXNJ) | ||
|---|---|---|---|
| Product: | [Eclipse Project] Platform | Reporter: | Jeff McAffer <jeffmcaffer> |
| Component: | UI | Assignee: | Eduardo Pereira <eduardo_pereira> |
| Status: | RESOLVED FIXED | QA Contact: | |
| Severity: | enhancement | ||
| Priority: | P3 | ||
| Version: | 2.0 | ||
| Target Milestone: | --- | ||
| Hardware: | All | ||
| OS: | Windows 2000 | ||
| Whiteboard: | |||
PRODUCT VERSION: 107 We should review all places we use MessageDialog.openError and use a ErrorDialog when we have the IStatus or access to it. Reviewed UI component and fixed all references that have a status |
When you get a build error (e.g., after saving a file with autobuild on), the UI puts up a dialog which says "Errors during build" The actual exception which is thrown back has much more information in it. Recent changes mean that the build will not fail completely when the first builder fails. We will continue to try and run all of the builders. As a result, the general form of the exception status is multistatus ("Errors during build") istatus ("builder 1 error") istatus ("builder 2 error") ... This seems like a prime candidate for the "Details" button. NOTES: