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.
dev build 200708110000 There seems to be some sort of parsing bug. When I open the attached Java file I see the following bugs: 1) When AbstractList isn't in the import list, Fix-Imports adds it. But then if you invoke it a second time it removes it. 2) I am expecting to get an editor hint to implement all abstract methods in AbstractList but this hint never comes up.
Created attachment 46480 [details] The source-code triggering the problem
The problem seems to be triggered by the following code sniplet: return AbstractList<Image>() notice the lack of "new" in between "return" and "AbstractList". I acknowledge this is a bug in my code but I expect Netbeans to handle it more gracefully. Ideally it should display a compiler error on that line and the "Fix Error" action should insert "new" in the appropriate location.
If you look int the tool tip of the lightbulb you'll see that the first error is illegal start of expression. That means that the Summary of the bug is incorrect. It is not always possible (or doable for performance reasons) to guess correctly what the user meant.
Overtake.