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.
Summary: | The type of ... is erroneous | ||
---|---|---|---|
Product: | java | Reporter: | mark01635 |
Component: | Hints | Assignee: | Svata Dedic <sdedic> |
Status: | RESOLVED DUPLICATE | ||
Severity: | normal | ||
Priority: | P3 | ||
Version: | 8.0 | ||
Hardware: | PC | ||
OS: | Windows 7 | ||
Issue Type: | DEFECT | Exception Reporter: |
Description
mark01635
2014-05-27 16:48:03 UTC
Just checked and this bug does not occur on NB 7.4. This is annoying, I had been using NB 7.4 for several hours before placing the previous comment, and then within 30 minutes it occurred on NB 7.4 exactly as on NB 8.0. I've been having this same issue for years. It seems to happen when you have JARs in your projects class path that get rebuilt. NetBeans detects they are rebuilt and rescans them automatically. But for some reason it gets confused intermittently (maybe it opens the file while it's still being written to?) and shows many of those "Type of ... is erroneous" messages. Although compiling the project using Ant works fine (the errors are bogus). The easiest fix is to delete the dependent JAR file and recompile it (which I do from the command line). Netbeans will then do a rescan and the error messages go away. When you click on the error badges in the number column to show suggestions netbeans just "beeps". Annoying little bug, but it's been happening a lot lately. Having tried the suggestion from pquiring for some time now, I can confirm that his suggestion does work. Perhaps there should be a re-scan option in the IDE somewhere. (In reply to Farmer_Mark from comment #4) > Having tried the suggestion from pquiring for some time now, I can confirm > that his suggestion does work. Perhaps there should be a re-scan option in > the IDE somewhere. There is a rescan option under the source menu -> scan for external changes. Unfortunately it is timestamp based so it doesn't solve the problem. I'm certain that netbeans is reading the dependency while it's being built by an external process before it's complete. The JAR is probably empty during it's scan so anything that was dependent on it will appear broken. But now netbeans will not re-read the file unless it's timestamp is changed. That's why deleting the file and rebuilding it solves the bogus errors. *** This bug has been marked as a duplicate of bug 252729 *** I am here for the share this amazing post need to follow here http://controlpanelwindows10.com and have to add control panel icon on desktop in windows 10. |