Bug 111281 - Build problems are not reported to user
Summary: Build problems are not reported to user
Status: CLOSED INVALID
Alias: None
Product: JDT
Classification: Eclipse Project
Component: Core (show other bugs)
Version: 3.1   Edit
Hardware: Macintosh All
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: JDT-Core-Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords: needinfo
Depends on:
Blocks:
 
Reported: 2005-10-01 05:01 EDT by Elliotte Rusty Harold CLA
Modified: 2009-08-30 02:09 EDT (History)
0 users

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Elliotte Rusty Harold CLA 2005-10-01 05:01:37 EDT
I recently spent several hours struggling with a failure to be able to run
anything  in two projects that depended one each other. I kept =getting
NoClassDefFoundErrors. Very frustrating. I eventually realized that Eclipse was
not actually compiling my classes into the bin directory (or anywhere else) and
that's why I couldn't run. It took a couple more hours to track this down to the
preference for "Build Path problems" specifically "Abort Build when errors
occur" and Incomplete path and circular dependencies being classified as errors.
Changing these to warnings fixed the problems. 

I am not sure whether these conditions should be warnings or errors by default.
However, I am sure that when I clean a project or build it, and it can't be
built due to one of these problems, that a dialog should be immediately shown to
the user telling them:

1. that the build failed
2. why it failed

This did not happen. The build failed silently, and the only indication I had
that it failed was that I didn't see the usual progress dialog telling me the
build was ongoing. Maybe there was a relevant message in the Tasks or Problems
view somewhere.  However, neither of these is displayed by default. Furthermore,
I did look through these pretty carefully, and I didn't find any such message.
If there was a message indicating the problem it was either too obscure or too
hidden amongst other problems for me to recognize.
Comment 1 Philipe Mulet CLA 2005-10-03 05:55:47 EDT
Are you developping Java code in the Java perspective ? If so, the problem view
is shown by default in it.
Comment 2 Elliotte Rusty Harold CLA 2005-10-03 06:16:05 EDT
You're right. I had turned off the problem view a while ago. However, that's not
quite the issue. I did look in the Problem view to see if there was any
indication of the problem. However, no message was shown there indicating the
problem. 
Comment 3 Philipe Mulet CLA 2005-10-03 10:39:15 EDT
Normally, you should get markers in the problem view indicating the reasons why
the builder refuses to build. If nothing appears, then clearly there is an issue. 
Comment 4 Philipe Mulet CLA 2005-10-03 10:42:50 EDT
Would it be somewhat similar to bug 110777 ? If not, please provide steps to
reproduce, then reopen.
Comment 5 Frederic Fusier CLA 2006-02-03 06:11:31 EST
Close as there have been no activity for more than 3 months.
Comment 6 Denis Roy CLA 2009-08-30 02:09:44 EDT
As of now 'LATER' and 'REMIND' resolutions are no longer supported.
Please reopen this bug if it is still valid for you.