views:

37

answers:

2

The little red 'x' on my Java class files in the project explorer (or package explorer) are missing. They were there...now they are gone.

This has happened before and usually a project clean, rebuild will do the trick. Also I unchecked the box that says abort build if build path error occurs.

Any ideas?

Edit: I am using the Maven M2Eclipse plugin.

+2  A: 

The X indicates a compile error in the file.

Your build process is fixing the errors somehow.

See: eclipse manual.

Tom Tresansky
I should have stated that the files in question DO have compiler errors. When I open then, I see the red "x" in the margin of the file...and the red squiggly underline of the problem area. It just doesn't show the issue in the problems view, or any of the explorer views -- just in the editor. The result is that I think everything is fine...run maven on the command line and watch the errors appear. When I then go into the problem file...boom...I see the compiler errors inside the editor...but still not in the explorer.
HDave
A: 

I turns out that in my particular case, I have a multi-module maven project. Disabling support for nested modules and then re-enabling support for nested modules did the trick. Apparently I needed to give m2eclipse a kick in the pants. What convinced me to do it was the fact that it was only Java Errors and Java Tasks that were the only problem markers not appearing -- and the Java Builder was missing from the list of builders.

HDave