Bug 427825 - Let subclasses of AbstractBundleContainer specify smoother progress monitoring for resolve()
Summary: Let subclasses of AbstractBundleContainer specify smoother progress monitorin...
Status: RESOLVED FIXED
Alias: None
Product: PDE
Classification: Eclipse Project
Component: UI (show other bugs)
Version: 4.4   Edit
Hardware: PC Windows 7
: P3 enhancement (vote)
Target Milestone: 4.4 M6   Edit
Assignee: Eike Stepper CLA
QA Contact:
URL:
Whiteboard:
Keywords: contributed
Depends on:
Blocks:
 
Reported: 2014-02-10 12:16 EST by Eike Stepper CLA
Modified: 2014-02-20 03:34 EST (History)
1 user (show)

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 Eike Stepper CLA 2014-02-10 12:16:30 EST 
My subclass of AbstractBundleContainer does all the resolve() work in resolveBundles() and resolveFeatures() just returns the already cached fFeatures.

In this scenario it's a little annoying that resolve() allocates one third of the overall work to resolveFeatures() in a hardcoded way.

https://git.eclipse.org/r/#/c/21720/ adds override points for subclasses with a work ratio different from 2/1. With the current defaults it should not impact existing subclasses, but maybe some of them could make use of the new methods, too.
Comment 2 Eike Stepper CLA 2014-02-20 03:34:37 EST 
Thank you for the quick reaction ;-)