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.
Summary: | Editor hint for all suggested imports | ||
---|---|---|---|
Product: | java | Reporter: | _ gsporar <gsporar> |
Component: | Hints | Assignee: | Svata Dedic <sdedic> |
Status: | NEW --- | ||
Severity: | blocker | CC: | markiewb |
Priority: | P4 | ||
Version: | 5.x | ||
Hardware: | All | ||
OS: | All | ||
Issue Type: | ENHANCEMENT | Exception Reporter: |
Description
_ gsporar
2006-04-24 20:09:30 UTC
How it should behaves if there is conflict in imports (typicaly class List is in several packages)?
>How it should behaves if there is conflict in imports?
I would say then it should behave the same way it does now. In other words, do
not offer the new "add all imports needed for this line" option *unless* there
is a single unique list of required imports. The down side, obviously, is that
the user interface will behave differently for different situations that might
*appear* to some users to be the same situation. I would say that is a price
worth paying.
|