Skip to main content



      Home
Home » Language IDEs » Java Development Tools (JDT) » Bogus "cannot be resolved to a type" error annotation
Bogus "cannot be resolved to a type" error annotation [message #218571] Tue, 08 November 2005 23:58 Go to next message
Eclipse UserFriend
I've been using Eclipse 3.1 for a couple of months on Mac OSX. In
general it's been a pretty good experience. But today a new and weird
problem has surfaced with the Java editor.

The editor is giving me tons of bogus error annotations indicating that
numerous types cannot be resolved. Note that my application builds just
fine, no errors at all and it runs just fine. But the editor if filled
with bogus error annotations.

Note that this problem is new, these errored files worked fine yesterday.

Another data point, if I open the file containing the "alledged"
undefined type, the associated bogus error annotations goes away until I
close this file.

I have tried cleaning and rebuilding to no avail (it's building just fine).

I searched the Bugzilla for this error but could not find anything like
this.

Anyone else see this type of problem? If so, is there any fix?

TIA

Ciao,

Rick D.
Re: Bogus "cannot be resolved to a type" error annotation [message #218602 is a reply to message #218571] Wed, 09 November 2005 12:20 Go to previous message
Eclipse UserFriend
This is a known JDT/Core problem with secondary types:
https://bugs.eclipse.org/bugs/show_bug.cgi?id=36032

We're currently working on it...

Richard Dunlap wrote:
> I've been using Eclipse 3.1 for a couple of months on Mac OSX. In
> general it's been a pretty good experience. But today a new and weird
> problem has surfaced with the Java editor.
>
> The editor is giving me tons of bogus error annotations indicating that
> numerous types cannot be resolved. Note that my application builds just
> fine, no errors at all and it runs just fine. But the editor if filled
> with bogus error annotations.
>
> Note that this problem is new, these errored files worked fine yesterday.
>
> Another data point, if I open the file containing the "alledged"
> undefined type, the associated bogus error annotations goes away until I
> close this file.
>
> I have tried cleaning and rebuilding to no avail (it's building just fine).
>
> I searched the Bugzilla for this error but could not find anything like
> this.
>
> Anyone else see this type of problem? If so, is there any fix?
>
> TIA
>
> Ciao,
>
> Rick D.
Previous Topic:integrate inline into build
Next Topic:code assist vs. content assist vs quick fix?
Goto Forum:
  


Current Time: Fri Apr 25 01:34:16 EDT 2025

Powered by FUDForum. Page generated in 0.03233 seconds
.:: Contact :: Home ::.

Powered by: FUDforum 3.0.2.
Copyright ©2001-2010 FUDforum Bulletin Board Software

Back to the top