views:

340

answers:

4

My project used to be fine - errors showed up in the file margin, the editor breadcrumb, the problems view and in the package explorer tree as little red X marks.

Somewhat spontaneously though, it's stopped working properly.

If I introduce an error into my code, it shows up in the file margin, and nowhere else. It takes a 'project clean' to make the red X's show up elsewhere.

Then if I fix the problem, the error is cleared from the file margin but the red marks persist elsewhere until I do another clean.

Why is it no longer showing errors properly in an automatic way?

I'm using Eclipse 3.5

+3  A: 

Did you uncheck Build Automatically?

matt b
Oh, for goodness sake :)Thanks.
izb
A: 

This is affecting me also. It ALSO used to show you in the navigator (back in eclipse europa) but that disappeared altogether. Now in galileo.... it is just buggy. So now i have to do an ANT build just to see if there are errors in my project before I can commit ??? That is not acceptable.

Guess i'll have to fork out for IntelliJ

A: 

Hi,

I got the same behaviour here and suppose this may be due to a different cause...(but did not check so far).

From what I found after googling some time is that JUnit is not working if you do not include AspectJ. If Eclipse 3.5 relies on aspects in the same way for error markers, this may be the cause such a behaviour (I uninstalled AspectJ because it's conflicting with Scala, which also uses a Weaving service).

If someone can also confirm this, please post here.

Alexander
Well, worked for me (after installing, errors were showing correctly) :-)
Alexander
A: 

Try fixing your build path, Java compiler, JRE first. If still no luck, You may want to take a look at project Properties-->Builders. Make sure "Java Builder" is there.

J - L