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: | Provide SPI for hooking into Fix Imports | ||
---|---|---|---|
Product: | java | Reporter: | Jesse Glick <jglick> |
Component: | Editor | Assignee: | Dusan Balek <dbalek> |
Status: | NEW --- | ||
Severity: | blocker | CC: | issues, jchalupa, mjanicek, tboudreau |
Priority: | P2 | Keywords: | API, UI |
Version: | 5.x | ||
Hardware: | All | ||
OS: | All | ||
Issue Type: | ENHANCEMENT | Exception Reporter: |
Description
Jesse Glick
2005-07-11 21:01:04 UTC
During development of NetBeans Module, its very common to copy portion of code from other modules sources. Of course, there are some imports that are missing. The steps that required to be done after the developer copied the code: Developer need to "Fix imports" If there are any missing dependencies, The "Fix Import" dialog will display the missing variables. User need to switch to project properties-> LIbraries -> Add Module dependencies, click on the "Add" button and type the missing class in the Filter. Again, in the editor, use the "Fix imports" . It will be a great value to have it in a single action (i.e "Fix imports" action will also add the missing dependencies to the project) Done as a separate hint for Maven projects: maven.hints/src/org/netbeans/modules/maven/hints/errors/SearchClassDependencyInRepo.java |