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: | AI in fix imports | ||
---|---|---|---|
Product: | java | Reporter: | tronicek <tronicek> |
Component: | Editor | Assignee: | Dusan Balek <dbalek> |
Status: | NEW --- | ||
Severity: | blocker | CC: | markiewb, terje7601 |
Priority: | P3 | ||
Version: | 6.x | ||
Hardware: | All | ||
OS: | All | ||
Issue Type: | ENHANCEMENT | Exception Reporter: |
Description
tronicek
2009-03-01 12:46:42 UTC
Good hint, thanks. If I have "Serializable" in my class & do "Fix Imports...", NetBeans proposes me "scala.Serializable" by default, with "java.io.Serializable" only as second option. I feel NetBeans should be smarter in this regard: * "scala.Serializable" is only available in the project because some transitive dependency deep in the hierarchy depends on Scala * java.io.Serializable is a Java SE class Some simple ordering that already seems much more logical to me is: * classes in the local project * java.*, javax.*, javafx.* * classes in direct Maven dependencies (i.e. dependencies in the "dependencies" section of the effective POM) * classes in transitive Maven dependencies (as e.g. scala.Serializable in this case) Please also note that there are already many issues related to NetBeans Fix Imports functionality & ways to improve it (bug 49573, bug 52088, bug 57853, bug 85968, bug 152192, bug 185612, bug 186368, bug 201222). Maybe it would be better to create a new umbrella bug & have it depend on all the aforementioned bugs? That way people can all vote on the umbrella bug & maybe priority will be raised. |