Bug 164487 – Better support for static imports in java editor

HOME / Community

Bug 164487 - Better support for static imports in java editor

Summary:

Better support for static imports in java editor

Status:	NEW

Product:	java
Component:	Editor
Version:	6.7
Platform:	All All

Priority:	P3 (vote)
Target Milestone:	TBD
Assigned To:	Dusan Balek
QA Contact:	issues@java

URL:
Whiteboard:
Keywords:

Depends on:	89258
Blocks:
	Show dependency tree / graph

Reported:	2009-05-05 14:00 by fommil
Modified:	2010-01-11 02:11 (History)

Issue Type:	ENHANCEMENT
Exception Reporter :

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note

You need to log in before you can comment on or make changes to this bug.

Description From fommil 2009-05-05 14:00:08

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 From igorminar 2009-05-26 19:30:49 -------

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 From fommil 2009-05-26 21:14:24 -------

@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.