Community
Participate
Working Groups
Steps 1) double click on the header tab of file1.java so the editor is not fullscreen. 2) edit file1.java so that it has an error. 3) switch to file2.java and do a build. The only notification that there is a problem is a tiny red x on the top of file1.java. This isn't nearly as obvious. This coupled with defect 44963, where a build can fail and the program still runs without any warning is very confusing behavior.
Moving to JDT/Text for comment.
The Problems view should also have been updated with the compiler errrors at the top of the list. So you have a suggestion as to how we could better notify the developer about compile problems?
The Problems view should come to front, causing the editor to get unmaximized. Unless you have that option turned off on the Workbench pref page. If you have the Problems view as a fast view, it will not need to unmaximize to show itself.
As per http://wiki.eclipse.org/Platform_UI/Bug_Triage_Change_2009
Remy is now responsible for watching the [EditorMgmt] component area.
This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet. If you have further information on the current state of the bug, please add it. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant.
