Bug 39031 - Project->Build does not report error.
Summary: Project->Build does not report error.
Status: RESOLVED WORKSFORME
Alias: None
Product: JDT
Classification: Eclipse Project
Component: Core (show other bugs)
Version: 2.1   Edit
Hardware: PC Windows 2000
: P3 normal (vote)
Target Milestone: 3.0 M3   Edit
Assignee: Kent Johnson CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2003-06-17 13:20 EDT by MG CLA
Modified: 2003-08-14 12:59 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 MG CLA 2003-06-17 13:20:45 EDT
Start a build on a project and then hit cancel.  Now try and use project->build,
it just pops up a dialog for a fraction of a second and that dialog is dismissed
without the classes being compiled.  The build command should display a dialog
stating the reason or at least notifing the user that the build didn't execute.

I know that it didn't execute because I went to the classes directory and
deleted one of the class files, then pressing ctrl-b the class file was not
resurrected.
Comment 1 MG CLA 2003-06-17 13:22:59 EDT
Refreshing and then trying a build works.
Comment 2 Kent Johnson CLA 2003-06-18 09:46:48 EDT
Deleting the class file from disk without a refresh inside Eclipse will not 
trigger a build. Eclipse does not search for changes made outside the 
environment until you tell it to...

As far as the original problem, I was unable to reproduce it. How many source 
file changes were involved in the first build? Was it a full build or an 
incremental that only affected 1-2 files?

If it was an incremental build, then I suspect the build finished before the 
cancel was detected... so there were no more changes to apply during the forced 
project build.
Comment 3 MG CLA 2003-06-18 13:07:50 EDT
It was an incremental build.  I'll try to get a better set of repro steps.  The
dialog was dismissed just like it thought there was nothing to build.   

Here is a question though, if eclipse knows there is nothing to build why bring
up the dialog at all?  Seems pretty pointless to pop-up something for a micro
second if all it is going to do is be flashed.  I suppose it does indicate that
eclipse received the command and I am not sure I wouldn't want anything to happen.
Comment 4 MG CLA 2003-06-18 13:26:51 EDT
Are you sure you can't repro?  Happens pretty much anytime I cancel a build.  I
can see in my source file markers along the side which when I hover say
"InputStreamReader can not be resolved or is not a type" but when I build, the
build dialog is just dismissed like eclipse believe it doesn't need to build. 
And there are no tasks listed.
Comment 5 Kent Johnson CLA 2003-06-23 14:14:52 EDT
What errors do you have on your project itself?

To see only these errors, select the project & the change the filter settings 
on the Task list to the 'On selected resource only'.
Comment 6 Kent Johnson CLA 2003-07-30 15:06:36 EDT
Is it still happening? Do you have more info?
Comment 7 MG CLA 2003-07-30 17:34:42 EDT
Doesn't seem to.  Now if I hit cancel in the middle of a build and then refresh
and try to build again I get the following message.  The message only goes away
if I then choose to rebuild project.

The project was not built due to "Problems encountered while deleting
resources.". Fix the problem, then try refreshing this project and rebuilding it
since it may be inconsistent.
Comment 8 Kent Johnson CLA 2003-07-31 09:26:42 EDT
That message is most often generated when we cannot delete resources because 
another application outside of eclipse is holding onto them.

What else are you running? Is anything else accessing files inside your 
workspace?
Comment 9 MG CLA 2003-07-31 14:00:46 EDT
When it first generates the message there might have been but I closed all apps
and then tried refresh and build but it refuses unless I say rebuild project. 
If Rebuild is able to do and not generate this error shouldn't build be able to
do it?  
Comment 10 Kent Johnson CLA 2003-08-12 15:03:23 EDT
'Build' detects deltas & performs a build as long as the deltas for the project 
are not empty. A 'rebuild' will always wipe the output folder and recompile as 
much as it can.

I've tried getting my project into a failed build state (which is what happened 
when some of your files couldn't be deleted), then fix/refresh the project & 
perform a 'build', not a 'rebuild'... but the 'build' works fine for me.

Reopen this PR if you can provide a reproduceable set of steps.