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

Bug 337961

Summary:	Builder should prompt to save unsaved files before building
Product:	[Tools] CDT	Reporter:	Lukas Felber <l.felber>
Component:	cdt-build	Assignee:	cdt-build-inbox <cdt-build-inbox>
Status:	RESOLVED DUPLICATE	QA Contact:	Andrew Gvozdev <angvoz.dev>
Severity:	normal
Priority:	P3	CC:	cdtdoug, me, yevshif
Version:	8.0
Target Milestone:	---
Hardware:	PC
OS:	Linux
Whiteboard:

Description Lukas Felber

2011-02-23 06:54:54 EST

Build Identifier: 

When building a project (user triggered) cdt should prompt if unsaved changes should be saved first.
I am aware that one can configure to automatically save before build. This is, however, not the feature I am looking for since if auto-save-before-build is disabled, unsaved changes get unnoticed, which causes misunderstanding.

I just coached novice C++ class (40 students) in at my university and 60% of the reported problems correlated to clicking the build button while having unsaved changes.

Reproducible: Always

Comment 1 Andrew Gvozdev

2011-02-23 10:02:22 EST

Such a dialog is there when you try to run a project (Run As), both in Java and C++. I think it makes more sense to adopt the dialog for build rather than for launch.

Comment 2 Lukas Felber

2011-02-24 02:33:46 EST

(In reply to comment #1)
> Such a dialog is there when you try to run a project (Run As), both in Java and
> C++.

I am aware that "Run As" is the more mature tool because it firstly saves resources (or asks if it should), then builds and in the end runs the program.

 I think it makes more sense to adopt the dialog for build rather than for
> launch.

But sometimes it makes sense to just want to see if the current program is "fine". (there is no need to run the program). So just do advise the students to directly use the "run" button does not solve the problem.

The core problem is that clicking on the "build" button causes misunderstanding, independent of that fact that "run as" does not.

Why should "build" behave differently to "run as" (expect that it should not run the program)?

Comment 3 Andrew Gvozdev

2011-11-06 14:27:27 EST

Same issue as in bug 362192.

*** This bug has been marked as a duplicate of bug 362192 ***