Community
Participate
Working Groups
I just started eclipse and it shows several errors in the editor that are bogus. See attachment.
Created attachment 11219 [details] bogus errors This picture is certainly better that a 1000 words from me.
Restarted eclipse and the problem went away.
Can you remember the message of the errors.
Hovering over the error indicator did not display a tooltip. I've also seen a similar problem where bogus errors are reported in the editor, navigator, and Problems view that say the import org.eclipse cannot be found. In both cases org.eclipse is underlined in the import declarations.
Created attachment 11239 [details] real error not propagated Here is a screenshot of a real error reported correctly in the editor, but nowhere else.
Bryan, there is a difference between errors shown in the editor and errors shown in other views. The editor shows error without the need of actually compiling the source. So if you change the code errors will show up immediatelly in the editor but not in other views. Views show the "build state" error. So editor and views are only in sync after a build. Does this sceanrio apply to the cases where you have seen the error only showing up in the editor. Moving to JDT/Core to comment on the error that the import org.eclipse can't be resolved.
Which build is this referring to ? Could be a classpath initialization issue, and we did resolve many of these in recent past.
*** Bug 64427 has been marked as a duplicate of this bug. ***
Another question: was your workspace built? I experienced similar behavior while copying classes for example from one project to another and having classpath problem in my second project. In this case, after the copy, you'll get lot of errors in the copied class if you edit it, but no error in problem views. After rebuilding my workspace, then problems views correctly reflect the errors that were displayed in the editor...
Pls reopen once requested info is available.
These problems are occuring on M9. In the case of comment #5, you will notice from the screenshot that the code in the editor has been saved (no * in the editor tab) but the error does not display in any of the other views, (and yes, I have incrimental build turned on so the workspace was built.
Thx for the info. Unfortunately we need more to understand what happen in your workspace... Would it be possible: 1- to attach the .classpath file of com.ibm.hdwb.data.ui project in which you get these errors, 2- to start eclipse with some jdt-core debug trace turned on (I will attach corresponding .options file) and then send us the resulting content of console output.
Created attachment 11275 [details] Option file for jdt-core debug trace ON. Detach this option file and start eclipse using -debug option as follow: start eclipse.exe -showlocation -debug <path to the .options file> -data %WORKSPACE% -consoleLog... or put this .options file in starting directory when you launch eclipse (it should be something like <eclipse install dir>/eclipse
I'll gladly provide the info as soon as the problem occurs again. Unfortunately, restarting Eclipse makes the problem go away.
ok, then I set it as resolved remind. Reopen it when you'll get this problem again and provide further information. thx
Closing as never reproduced in a long time
As of now 'LATER' and 'REMIND' resolutions are no longer supported. Please reopen this bug if it is still valid for you.
