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

Bug 116623

Summary: [Markers] Java compilation failures no longer flagged in
Product: [Eclipse Project] Platform Reporter: Peter Kidson <peterkidson-eclipzilla>
Component: UIAssignee: Tod Creasey <Tod_Creasey>
Status: RESOLVED DUPLICATE QA Contact:
Severity: normal    
Priority: P3    
Version: 3.1.1   
Target Milestone: ---   
Hardware: PC   
OS: Windows XP   
Whiteboard:
Attachments:
Description Flags
jpeg of the red boxes AFTER an attempted launch
none
jpeg of out-of-date error none

Description Peter Kidson CLA 2005-11-16 03:31:20 EST 
In Version: 3.1.1, Build id: M20050929-0840, if you make a change to a .java 
file that say removes a method referred to in another .java file,  you no 
longer get the warning  ( the little X inside a red box ) straight away.  You 
only discover get them after you next attempt a launch ( which does still warn 
you with a text message though).
Comment 1 Peter Kidson CLA 2005-11-16 03:33:49 EST 
Created attachment 30043 [details]
jpeg of the red boxes AFTER an attempted launch

This is what you should (and used to) get as soon as you cause a compile error
Comment 2 Peter Kidson CLA 2005-11-16 03:44:02 EST 
Furthermore,  if you do make an error which is shown, and then correct it,  
the error message in the Problems Tab fails to clear.
For example - see 2nd attachment - I had deleted the word "package" on the top 
line.  I corrected it, saved, but the error remained.
Comment 3 Peter Kidson CLA 2005-11-16 03:46:43 EST 
Created attachment 30046 [details]
jpeg of out-of-date error

The error message remains after the error has been corrected and the file saved
Comment 4 Tod Creasey CLA 2006-04-07 16:04:04 EDT 

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