[jsbeal]

Hello, all –

I have been experiencing some anomalous behavior within the Package Explorer that is becoming troublesome. One of the projects I work with flags a compiler error at the top level (red box with white cross over the topmost package icon), but these icons do not propagate down the package hierarchy to any particular class.

I have experimented by inputting a known error into the editor and saving – the error was flagged by the code inspector in the editor window, but this flag did not get posted in the package explorer. A subsequent build did not change this, nor did cleaning my workspace.

I have turned off project validations, as I had no need for anything but the standard Java code inspector, but turning them back on again did nothing. Does anyone have any experience with something like this, or an idea for how to fix it?

Thanks,

Justin

[Loyal Water]

Hi Justin,
Can you switch to a brand new workspace, create a new project there and see if you get the same behaviour.

This could be an installation / configuration too.

[jsbeal]

Switching to a new workspace and creating a new project within that new workspace reverts to default (correct) behavior. The other projects within the original workspace, though, also display the default (correct) behavior. It is only one specific project that causes problems, which leads me to believe it is a project specific problem.

Thanks!

[jsbeal]

Copying the project contents into a temporary directory and then back to the original directory solved the problem. Possibly caused by some artifacts from prior development – I can’t speculate more than that.

[Author]

Posts