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.
NetBeans desperately needs a simple way to just dump all accumulated information about classes in a project and rebuild that information. When changing a class or interface, the IDE sometimes doesn't manage to update everywhere, leading to erroneous error messages like mismatching types, missing method overloads, etc. For example, when adding methods to an interface definition, the IDE doesn't realise that the functions have been added and marks calls as errors, even though the compiler has no problems at all. So far, the only way to resolve those issues seems to be to re-import the project from scratch, losing all settings made. I tried deleting large parts of ~/.netbeans and the nbproject and build directories, which didn't change anything.
Have you tried to delete ~/.netbeans/5.5/var/cache/mdrstorage directory? This is the only place, where all the information about classes are stored.
I tried that. I even tried deleting the whole var/cache directory.
Then we'll need more info for investigating the problem. Can you post exact steps to reproduce? What kind of project do you use?
I can't seem to reproduce the problem anymore. Anyway: when the problem occurred, I had imported the Network Calculator available at: http://disco.informatik.uni-kl.de/content/Downloads as a "Java Project with existing sources", and after some other changes, extended the interface "PWLFunction" by some methods, implemented the methods in the classes implementing the interface, and used those methods in FunctionView after the cast on line 182 in FunctionView.java. The IDE consequently failed to register the updated interface and marked every use of the new methods *only in FunctionView*. The problems even persisted after re-importing the sources after cleaning out NetBeans data, and even after deleting large parts of the user-specific NetBeans configuration. I should say that the source/project directory was on an NFS mount. May there have occurred a problem because of this? (Slight timestamp problems, locking, ...)
Reorganization of java component
This issue is not valid in current builds any more. Java support was completely redesigned in 6.0 time frame. Please use NetBeans 6.0 and later.