Summary: | Smoke 114: Progress reporting when switching to different default VM (1GEHXMV) | ||
---|---|---|---|
Product: | [Eclipse Project] JDT | Reporter: | Dirk Baeumer <dirk_baeumer> |
Component: | Core | Assignee: | Jerome Lanneluc <jerome_lanneluc> |
Status: | VERIFIED FIXED | QA Contact: | |
Severity: | normal | ||
Priority: | P4 | ||
Version: | 2.0 | ||
Target Milestone: | 2.1 M3 | ||
Hardware: | All | ||
OS: | Windows 2000 | ||
Whiteboard: |
Description
Dirk Baeumer
2001-10-10 22:59:43 EDT
moved to 'active' PRODUCT VERSION: Smoke 114 defer Moving to debug *** Bug 3802 has been marked as a duplicate of this bug. *** marking as a 2.1 candidate Found that building projects reports progress properly now. However, before building, we update the JRE classpath varaiable, which causes JavaCore to execute "SetClasspathOperations" on each affected project. Each operation performes a "begin task" on the same progress monitor (via JavaCore.setClasspathVariables(...)). Thus, progress is reported for the first classpath change, but then the monitor is at 100% and still making updates. Since it is JavaCore that determines the number of affected projects and operations to perform, it needs to update the monitor. Moving to JCORE. Jerome - could we use the batching mechanism to improve this behavior ? Fixed post action in updateVariableValues() to pass null as the progress monitor (setRawClasspath is instantaneous now). Verified. |