This Bugzilla instance is a read-only archive of historic NetBeans bug reports. To report a bug in NetBeans please follow the project's instructions for reporting issues.
The folder in the "Files" view, or the package folder in the "Projects" view is marked with an error emblem (exclamation mark in the red circle), while no files under that folder have the same emblem. It is obvious that the tool indeed sees some problem there, but it does not show what exactly is wrong. This is persistent; restarting the tool, closing and re-opening the project does not help.
Can you provide more information? (build number, jdk version)
I confirm this one. Product Version: NetBeans IDE 6.0 Beta 1 (Build 200709141330) Java: 1.6.0_02; Java HotSpot(TM) Client VM 1.6.0_02-b05 System: Windows XP version 5.1 running on x86; Cp1252; de_DE (nb) The problem is located in the configuration files under .netbeans\6.0beta1\var\cache\index\ Removing that folder & restart resolved the problem for me. But i did some further investigation: In my situation, there were some files under .netbeans\6.0beta1\var\cache\index\0.4\s68\errors\batch\calculators (The meaning of 's86' is explained by a file 'segments', which is located in the folder '../0.4') batch.calculators is one of those packages which shows a red exclamation mark without reason. Well, within that cache directory, there are three files: IntIntKey.err nonrecursive.dep recursive.dep "IntIntKey" was the name of class that 'lived' in that package some time ago. Then i decided to move that class to another package (by using refactoring?). Well i don't know whether this is the reason for the problem or not. Anyway, by just renaming 'recursive.dep' to 'recursive.dep_' i solved the problem for that particular package So i assume, there are some situations, where the IDE is not aware of some cached error information not in sync anymore... @lilyevsky: Can you track down the problem this way?
ok, here's how to reproduce: Create a java class in package x.y.z. The class may be totally empty. Compile it. Introduce an error by writing 'x;' in the classes body. Save Red marks are shown. Now use "Refactor/Move" on that class to move it to another package.
perhaps this is duplicate of http://www.netbeans.org/issues/show_bug.cgi?id=104665
seems to be no longer reproducible, marking as duplicate of issue 104665 *** This issue has been marked as a duplicate of 104665 ***