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

Bug 470927

Summary: Problems view doesn't log obvious error
Product: [Eclipse Project] JDT Reporter: Taro Kyo <taro_k>
Component: UIAssignee: JDT-UI-Inbox <jdt-ui-inbox>
Status: CLOSED DUPLICATE QA Contact:
Severity: normal    
Priority: P3 CC: daniel_megert, markus.kell.r, stephan.herrmann
Version: 4.4.2   
Target Milestone: ---   
Hardware: PC   
OS: Windows 8   
Whiteboard:
Attachments:
Description Flags
Screenshot of obvious error, with highlighted arrows and text describing what the viewer should be looking at.
none
GIF in action. none

Description Taro Kyo CLA 2015-06-24 21:35:20 EDT
Created attachment 254680 [details]
Screenshot of obvious error, with highlighted arrows and text describing what the viewer should be looking at.

For some reason, Problems view isn't logging an obvious error. 

Steps to Reproduce:

1. Have Eclipse Luna Stable Release 2, Build id: 20150219-0600, brand new.
2. Open up an old Java project.
3. In any Java file, on any line, enter a new line.
4. Type the word, "error", without quotes.
5. The IDE will report that there's an code parsing error, but the Problems view will not validate/update to reflect upon this.

See attached screenshot.
Comment 1 Taro Kyo CLA 2015-06-24 21:37:16 EDT
Created attachment 254681 [details]
GIF in action.
Comment 2 Stephan Herrmann CLA 2015-06-25 03:44:27 EDT
(In reply to Taro Kyo from comment #0)
> Created attachment 254680 [details]
> Screenshot of obvious error, with highlighted arrows and text describing
> what the viewer should be looking at.

The screen shot shows that the file has not been saved (see "*Area.java").
What happens when you save it?
Comment 3 Markus Keller CLA 2015-06-25 12:19:13 EDT
The Problems only shows build problems, not temporary issues in an unsaved editor.

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