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.

Bug 163573 - Fix imports enhancement
Summary: Fix imports enhancement
Status: RESOLVED DUPLICATE of bug 52088
Alias: None
Product: editor
Classification: Unclassified
Component: Completion & Templates (show other bugs)
Version: 6.x
Hardware: PC All
: P3 blocker (vote)
Assignee: Dusan Balek
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2009-04-24 11:37 UTC by hazgod
Modified: 2009-09-23 16:08 UTC (History)
1 user (show)

See Also:
Issue Type: ENHANCEMENT
Exception Reporter:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description hazgod 2009-04-24 11:37:15 UTC
I use Fix Imports regularly. One thing I have noticed is that it usually doesn't select the right class to import. What
I would suggest is a list, possibly globally and per project, that would specify by name the class that should be defaulted.

An example: I use the Connection class in a large majority of my classes. When you run Fix Imports, there are currently
6 classes called Connection. Now the only one I am interested in most of the time is java.sql.Connection. It is
currently defaulted to com.mysql.jdbc.Connection. Maybe I should be using that, I don't really know. But
java.sql.Connection is what I use everywhere so it would be nice if, for "Connection", it defaulted the list of possible
imports to java.sql.Connection
Comment 1 trcorbin 2009-05-13 21:09:31 UTC
Very similar to 52088
Comment 2 Vitezslav Stejskal 2009-09-23 16:08:27 UTC

*** This issue has been marked as a duplicate of 52088 ***