Logo Questions Linux Laravel Mysql Ubuntu Git Menu
 

Make Eclipse NOT run project on errors

Tags:

eclipse

Is it possible to make Eclipse (Helios SR2) NOT run your project on errors, instead of prompting for an answer or run anyway ?

Scenario:

In eclipse, I hit the Run button. There are compilation errors. Eclipse asks me if I would still like to continue with the run. I have the options of "Yes" and "No". I can also tick "Always run without asking".

In Eclipse Preferences, under Run/Debug > Launching there are radio buttons for "Continue launch if project contains errors", but they only give 2 options, "Always" or "Prompt". Other sections on that page give the options "Never", but not this one.

Now. I'd just like to never run if there are errors, without any prompt (a console message would be just perfect, but not required). Is that possible ?

like image 303
olafure Avatar asked Jun 29 '11 09:06

olafure


People also ask

How do you stop a project from running in Eclipse?

It can typically be found somewhere along the bottom of your screen. If you can't find the console, go to Window > Show View > Console. Then you will see a red stop button as part of the console. This will terminate the running program, leaving the console messages behind.

How do I fix Eclipse errors?

You have open eclipse. ini file and change -vm path to correct JDK location. In my case it's /Library/Java/JavaVirtualMachines/jdk1.

How do I view project errors in Eclipse?

From the main menu, select Window > Show view > Other. Then select General > Error Log. The error log is displayed, showing the following information for each error: The status of the error (for example, error or warning)

How do you stop a building in Eclipse?

"stop build" in eclipse,however,the command button truely exists in VC6. 0. In the right corner at the bottom there should be an icon which would open the progress view. There you can click the stop button.


2 Answers

IMHO this seems like a very dangerous and error promoting behaviour (especially the "always run without asking" selection!)

If there are compiler errors, then I want the run attempt aborted so I can fix them, and if the code runs, then I want to be able to rely on it to (at least) be free from compiler errors... Why on earth would I want to risk running code that contains compiler errors, and spend hours debugging weird behaviours in the execution, when the root of the problem is already known?

Wouldn't it be more natural to have "never" as default, and "promp" as an option?

like image 181
Engztrom Avatar answered Sep 20 '22 16:09

Engztrom


Preferences > Run/Debug > Launching > Continue launch if project contains errors > Prompt Voila!

like image 30
Zayat Avatar answered Sep 19 '22 16:09

Zayat