Community
Participate
Working Groups
Build Identifier: 20110916-0149 I have the same problem as in the bug 265009 but in Eclipse Indigo since SR1: The navigator view stopped displaying compiler warning/error icons at java files. It works in vanilla 3.7. I've tried changing workspace. Reinstalling fresh eclipse - removing all plugins. Updating vanilla Indigo to SR1. Nothing helps - once SR1 is in, I don't have error/warning icons in Navigator view. I still have these in Package/Project Explorer views. I have the same effect on various installations and OSes including, for example, Win 7. Reproducible: Always Steps to Reproduce: 1. Edit java file, make an error in that. 2. Switch to Navigator view 3. The file editor and the package/project explorer views will show a small error icon on the file, package and so on, but the navigator view - won't.
Created attachment 206072 [details] Screenshot depicting the state in question. This never worked (I tried 3.1) and certainly does not work in 3.7.0.
*** This bug has been marked as a duplicate of bug 265009 ***
*** This bug has been marked as a duplicate of bug 2108 ***
Created attachment 206074 [details] Screenshot depicting my state in the question :) Always worked for me... Attaching just for the sake of my sanity :) It's a pity, the Navigator view is being phased out, but I'll try to live with it if it's all set in stone...
(In reply to comment #4) > Created attachment 206074 [details] > Screenshot depicting my state in the question :) > The screenshot also shows that there are many things installed. One of the additional bundles might provide the error ticks (I think it night be WTP). If so, you'd need to file the bug there (i.e. ask why it's broken now).
(In reply to comment #5) > (In reply to comment #4) > > Created attachment 206074 [details] [details] > > Screenshot depicting my state in the question :) > > > The screenshot also shows that there are many things installed. One of the > additional bundles might provide the error ticks (I think it night be WTP). If > so, you'd need to file the bug there (i.e. ask why it's broken now). Ah-ha, thank you very much for the pointer.