Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.

Bug 348764

Summary: Add progress reporting to system parts initialization
Product: z_Archived Reporter: Justin Spadea <jspadea>
Component: EDTAssignee: Justin Spadea <jspadea>
Status: CLOSED FIXED QA Contact:
Severity: enhancement    
Priority: P3    
Version: unspecified   
Target Milestone: ---   
Hardware: PC   
OS: Linux   
Whiteboard:

Description Justin Spadea CLA 2011-06-08 11:17:22 EDT 
A compiler's system environment is lazily loaded. The builder is usually what invokes this first, so on its first build it sits at a particular % in the progress view for anywhere from a couple seconds to tens of seconds while the system environment is loaded (depending on JRE, system load, etc). To the user it looks stuck on something.

At the very least we should indicate "Initializing system environment", but a better approach would be to report the progress of loading the parts.

We can't just pass in an IProgressMonitor because that class doesn't exist in SDK. For fine-grained progress reporting we should add a new interface that can be passed around the init code. This would show the current eglar/mofar being loaded, as well as actually show the progress monitor increase as parts are loaded. We would only need some of the methods from IProgressMonitor in our interface. The builder's implementation would simply wrap the IProgressMonitor.
Comment 1 Justin Spadea CLA 2011-06-09 13:48:20 EDT 
Implemented as discussed in the original comment, except that a new interface wasn't created. There was already an IBuildNotifier interface available to SDK.
Comment 2 Justin Spadea CLA 2011-06-10 12:33:03 EDT 
Verified in 6/9/11 build