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.
[ BUILD # : 200502271900 ] [ JDK VERSION : J2SE 1.5.0_01 ] See attached test case and screen dump. Basically, the Debugger does not understand about static import methods, so you cannot see the result of such a function call.
Test Case: package nbBugs; import java.util.Collection; import static nbBugs.HelperFunctions.*; class HelperFunctions { static boolean isEmpty(Collection coll) { return (coll == null || coll.isEmpty()); } } public class StaticImport { public static void main(String args[]) { boolean b = isEmpty(null); System.out.println(b); } }
Created attachment 20572 [details] Show debugger problem when highlighting isEmpty(null)
I can not fix it for nb41. Debugger uses old src model, which does not support JDK1.5 features.
Reproduced. The import is recognized, but it's not treated as static. Therefore the imported method is not found.
*** Issue 120497 has been marked as a duplicate of this issue. ***
The problem has been reproduced, analyzed, but not fixed. As mentioned in 120494, this is an important feature now that Java5 is "mainline". Since no practical workaround exist for that problem, per QA guidelines, and to raise visibility of that issue, I'm moving to P2.
We know about several problems in NetBeans evaluator, which are of similar severity. I've created an umbrella issue for that already - issue #108873. We plan to rewrite the evaluator algorithm from scratch into NetBeans 6.1, since addressing these issues in the current code is problematic.
Hmm, o, but when is NetBeans 6.1 planned? I see no mention of it in http://www.netbeans.org/community/releases/roadmap.html
I do not know, it's not scheduled yet. But fixing evaluator is not doable into 6.0, we're approaching code-freeze. We've talked about it in the bug-fixing period, but there were other, more severe defects. We expect to work on the rewrite after 6.0 is released, so it can be either a part of 6.1 or perhaps some hot-fix update on Update Center. This is still TBD.
Fixed in the new evaluator algorithm - see issue #108873.
Verified ... and Closing all issues resolved into NetBeans 6.7 and earlier.