JB 2005 foundation - free version has the following functionality.

Fix import - 
  removes un-necessary,un-used imports, 
  sorts them seperating each package block by an empty line, 
  configurable to include package decl or full class name decl.
  i.e. import javax.swing.*; or import javax.swing.JLabel;
  you can even configure the package depth.

NB does not have the above - please provide this.

In fact NB does "import resolving" which is brilliant and JB does have this
functionality.

But why can't the import resolving be done as you type. Why can't this be
configurable.  I notice that NB finds the class and hence provides code
completion for the relevant class. But after that you have to explicitly ask to
fix imports !!  why not have a configurable option such that the editor can
include the import as we type ? 

If the class is unresolved a window should pop up to say this and code
completion should not work ! 

If the class is ambiguous a window should pop up to allow selection and then the
code completion logic should kick in !!

This would be spectacular.

In a nutshell if code completion works , the editor already knows what should be
included.

cheers