Bug 230307 - I want a "Never" option for "Continue launch if project contains errors"
Summary: I want a "Never" option for "Continue launch if project contains errors"
Status: ASSIGNED
Alias: None
Product: Platform
Classification: Eclipse Project
Component: Debug (show other bugs)
Version: 3.4   Edit
Hardware: PC Windows Vista
: P5 enhancement (vote)
Target Milestone: ---   Edit
Assignee: Platform-Debug-Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
: 76873 273690 489140 (view as bug list)
Depends on:
Blocks:
 
Reported: 2008-05-05 18:34 EDT by Scott Schafer CLA
Modified: 2016-03-14 06:32 EDT (History)
9 users (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Scott Schafer CLA 2008-05-05 18:34:23 EDT
...because I never, ever, not once in my 20 years of software development have EVER wanted to launch if the build failed.
Comment 1 Paul Webster CLA 2008-05-05 19:25:49 EDT
(In reply to comment #0)
> ...because I never, ever, not once in my 20 years of software development have
> EVER wanted to launch if the build failed.

The enhancement request is valid, but there are many reason to continue (which is why this is the default).

Eclipse incremental build will still create .class files (with methods that throw an Error if they were the ones with compile problems).  Depending on what code paths are being exercised, it is acceptable to launch with errors.

Also, tools (like the API tooling) generate errors for API failures (which are build errors that are not a compile error).

As an aside ... while we could never ask the user again, we'll still have to pop up a dialog ... you shouldn't just stop giving a user feedback when he clicks run (that used to work, but suddenly doesn't do anything).

PW
Comment 2 Darin Wright CLA 2008-05-06 08:58:31 EDT
We used to have a never option (long ago...), but because there was no feedback when the user pressed run/debug - it was not useful. We still have to prompt the user to tell them there are errors - so in this case, "prompt" should suffice. Just press the cancel option when prompted.
Comment 3 Curtis Windatt CLA 2009-04-27 08:44:14 EDT
*** Bug 76873 has been marked as a duplicate of this bug. ***
Comment 4 Curtis Windatt CLA 2009-04-27 08:46:24 EDT
*** Bug 273690 has been marked as a duplicate of this bug. ***
Comment 5 web CLA 2009-04-27 09:14:26 EDT
Instead of popping up a dialog box, you could simply open / show the errors pane.  This provides feedback that the compilation happened, and provides the user easy access to start fixing the errors.  It seems to be common behavior among other IDE's.
Comment 6 arne anka CLA 2009-04-27 09:55:29 EDT
@comment #2

so?
why is it so hard to own up to the idea that your user have some little intelligence?
if the user decides to enable "never" -- let him. he/she should be able to work with that decision.

if you want to give feedback, show an icon in the lower border like the team plugin does.
in most case the user already has some output on the console, showing what went wrong far better than a popup harshly breaking the workflow because it forces you to focus on that rather uninformative and illogical thing instead of the output of your program.

as long as it is possible to make the dialog remember my positive decision, i wnat it to remember my negative decision, too -- i am an adult and i know what i do. i don't need some kind of benevolent  warden making my decision for me.
Comment 7 Dani Megert CLA 2016-03-14 06:21:10 EDT
*** Bug 489140 has been marked as a duplicate of this bug. ***
Comment 8 Dani Megert CLA 2016-03-14 06:22:15 EDT
Reopening for further consideration.