Please use the Apache issue tracking system for new NetBeans issues (https://issues.apache.org/jira/projects/NETBEANS0/issues) !!
Bug 164487 - Better support for static imports in java editor
Better support for static imports in java editor
Status: NEW
Product: java
Classification: Unclassified
Component: Editor
6.x
All All
: P3 with 3 votes (vote)
: TBD
Assigned To: Dusan Balek
issues@java
:
Depends on: 89258
Blocks:
  Show dependency treegraph
 
Reported: 2009-05-05 14:00 UTC by fommil
Modified: 2011-10-20 08:04 UTC (History)
1 user (show)

See Also:
Issue Type: ENHANCEMENT
:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description fommil 2009-05-05 14:00:08 UTC
The Java Completer should offer static methods for completion as if they were local. This already happens for already imported static methods, 
but it should also do this for static methods from user-specified classes, potentially with NetBeans shipping a good stock supply as default. This requires a 
UI similar to the "Java Code Completer Excluder" that I added as part of issue 125060.
Comment 1 igorminar 2009-05-26 19:30:49 UTC
There are several dupes of this RFE/bug report. Mainly:
http://www.netbeans.org/issues/show_bug.cgi?id=89258
http://www.netbeans.org/issues/show_bug.cgi?id=71249

It would be great to see this in 6.7
Comment 2 fommil 2009-05-26 21:14:24 UTC
@igorminar they are related, but not dupes. The first is about the hints system and the second for "Fix Imports". This RFE is for the code completer.
Comment 3 Jesse Glick 2011-10-19 15:32:57 UTC
Still valid in 7.1?
Comment 4 Dusan Balek 2011-10-20 08:04:20 UTC
Unfortunately, it is still valid. The main blocker is a fact that only those class members (methods, fields) that come from sources are currently indexed (so methods like Math.abs(...) that come from rt.jar are not indexed yet).


By use of this website, you agree to the NetBeans Policies and Terms of Use. © 2014, Oracle Corporation and/or its affiliates. Sponsored by Oracle logo