Bug 2052 - Build Error info not accessible (1GDUXNJ)
Summary: Build Error info not accessible (1GDUXNJ)
Status: RESOLVED FIXED
Alias: None
Product: Platform
Classification: Eclipse Project
Component: UI (show other bugs)
Version: 2.0   Edit
Hardware: All Windows 2000
: P3 enhancement (vote)
Target Milestone: ---   Edit
Assignee: Eduardo Pereira CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2001-10-10 22:25 EDT by Jeff McAffer CLA
Modified: 2002-05-30 15:01 EDT (History)
0 users

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Jeff McAffer CLA 2001-10-10 22:25:26 EDT 
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:
Comment 1 DJ Houghton CLA 2001-10-29 17:48:19 EST 
PRODUCT VERSION:

107
Comment 2 Eduardo Pereira CLA 2002-02-11 16:56:12 EST 
We should review all places we use MessageDialog.openError and use a 
ErrorDialog when we have the IStatus or access to it.
Comment 3 Tod Creasey CLA 2002-05-30 15:01:03 EDT 
Reviewed UI component and fixed all references that have a status