Cannot be resolved errors in Java import statements

This topic contains 1 reply, has 2 voices, and was last updated by Profile photo of Riyad Kalla Riyad Kalla 10 years, 4 months ago.

Viewing 2 posts - 1 through 2 (of 2 total)
  • Author
  • #270315 Reply
    Profile photo of paisleyblue

    I am using a professional edition of MyEclipse IDE version 5.1.1 GA for almost three months now. Out of the blue, I started getting ‘cannot be resolved’ errors in the Java sources in the import statements and object references throughout (red lines, red X boxes). Nothing has changed in the Build Path, and those packages referenced do exist.

    Previously, the same problem would happen in the trial version – especially with JSP files. So I upgraded to a paid subscription, and this just started happening again. Any ideas on how I can resolve this? (Its annoying, plus the debugger doesn’t like the errors.)

    #270358 Reply
    Profile photo of Riyad Kalla
    Riyad Kalla

    Please check your problem view and/or open your project properties and go to Java Build Path > Libraries and see if any of your libraries are User Libraries have error or warning markers next to them.

    There was a long-standing bug in the Eclipse platform where User Libraries would become un-bound from their library contents that was finally fixed in 3.3M6… entire thread here:

    you’ll notice the symptoms are very similar to your own.

Viewing 2 posts - 1 through 2 (of 2 total)
Reply To: Cannot be resolved errors in Java import statements