Bug 3717 - Smoke 114: Progress reporting when switching to different default VM (1GEHXMV)
Summary: Smoke 114: Progress reporting when switching to different default VM (1GEHXMV)
Status: VERIFIED FIXED
Alias: None
Product: JDT
Classification: Eclipse Project
Component: Core (show other bugs)
Version: 2.0   Edit
Hardware: All Windows 2000
: P4 normal (vote)
Target Milestone: 2.1 M3   Edit
Assignee: Jerome Lanneluc CLA
QA Contact:
URL:
Whiteboard:
Keywords:
: 3802 (view as bug list)
Depends on:
Blocks:
 
Reported: 2001-10-10 22:59 EDT by Dirk Baeumer CLA
Modified: 2002-11-15 06:54 EST (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 Dirk Baeumer CLA 2001-10-10 22:59:43 EDT 
- create a new workspace 
	- set J9 as default VM
	- load JUnit
	- switch back to JDK 1.2.2 as default VM
	- press OK in Preference Dialog
	- you get a progress monitor dialog
	observe: progress is still reported (via subtasks) but the progress bar is at its end.
		


NOTES:
EG (5/29/2001 11:44:23 AM)
	could be improved but not critical.
Comment 1 Martin Aeschlimann CLA 2001-10-16 11:12:28 EDT 
moved to 'active'
Comment 2 DJ Houghton CLA 2001-10-24 07:18:00 EDT 
PRODUCT VERSION:
	Smoke 114
Comment 3 Erich Gamma CLA 2001-11-10 18:41:43 EST 
defer
Comment 4 Dirk Baeumer CLA 2002-07-25 10:48:10 EDT 
Moving to debug
Comment 5 Darin Wright CLA 2002-07-29 09:28:38 EDT 
*** Bug 3802 has been marked as a duplicate of this bug. ***
Comment 6 Darin Wright CLA 2002-08-12 11:53:03 EDT 
marking as a 2.1 candidate
Comment 7 Darin Wright CLA 2002-08-29 15:40:16 EDT 
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.
Comment 8 Philipe Mulet CLA 2002-10-28 09:07:09 EST 
Jerome - could we use the batching mechanism to improve this behavior ?
Comment 9 Jerome Lanneluc CLA 2002-10-30 07:40:49 EST 
Fixed post action in updateVariableValues() to pass null as the progress 
monitor (setRawClasspath is instantaneous now).
Comment 10 David Audel CLA 2002-11-15 06:54:20 EST 
Verified.