Bug 4147

Summary:	Launcher progress has "Build Completed" (1GJ4MAY)
Product:	[Eclipse Project] JDT	Reporter:	Nick Edgar <n.a.edgar>
Component:	UI	Assignee:	Martin Aeschlimann <martinae>
Status:	RESOLVED FIXED	QA Contact:
Severity:	normal
Priority:	P1
Version:	2.0
Target Milestone:	---
Hardware:	All
OS:	Windows 2000
Whiteboard:

Description Nick Edgar

2001-10-10 23:06:50 EDT

Whenever I launch a program, the progress dialog shows "Java Build Completed" 
even though it doesn't run the builder first (I have auto-build off).

NOTES:
EG (8/31/2001 9:40:02 AM)
	when you launch a program JDT performs a build of the project that contains the
	launched target. The rational is that the user almost always wants to run the
	latest code. For 2.0
	we should provide more control over the pre-launch build behaviour.
	We should provide options for:
	* build current project before launch/debug
	* build workspace before launch/debug
	* don't auto build.
	Both options should honor the workbench preference to auto save
	modified CUs.

NE (9/17/01 10:06:22 AM)
	Agree.  But I originally filed the PR because it seemed like it was giving me this message
	without actually doing a build.  I'll see if I can reproduce this.

EG (17.09.2001 16:38:36)	
	speculating, could this be a consequence of not honoring the auto save preference
	of modified CUs. This means the builder was run but didn't build anything
	since the CUs were not saved.

Comment 1 Martin Aeschlimann

2001-10-16 11:14:09 EDT

moved to 'active'

Comment 2 DJ Houghton

2001-10-29 17:34:27 EST

PRODUCT VERSION:
132

Comment 3 Erich Gamma

2001-11-11 11:18:42 EST

eventually, DEBUG will implement the Java launching code, but we should still 
improve the existing behaviour

Comment 4 Martin Aeschlimann

2001-11-12 09:59:17 EST

The progress monitor message issue should be fixed in the current build.
The problem was the improper use of the progress monitor (no subprogress 
monitor used)
For the other request (ask the user about building) there is another PR (4023)