I often use the same libraries in my projects and "Fix Imports" often suggests the "wrong" class from that perspective.  I'd like to be able to configure an ordering of classes so the "right" class comes up first.  That would save me a lot of time.

For example, I use the Restlet (http://www.restlet.org/) libraries and they use the class "Resource" a lot.  Resource comes up with the following choices in this order:

   javax.annotation.Resource
   org.restlet.data.Resource
   sun.misc.Resource

which is just sorted lexicographically.  I'd prefer the ability to configure in my preferences that org.restlet.data.Resource is the class selected.

In addition, there seems to be some obvious general tweaks that would be good to implement overall
selection choice:

  * org.*, com.*, java.*, and javax.* packages should come before others.  This helps
    distinguish between things like "apple.laf.CoreUIConstraints.Variant" and classes
    like org.restlet.representation.Variant.  The apple.* is probably, statistically speaking, almost
    always the wrong choice.

  * java.* before org.*
  * org.* before com.*

I think some set of default rules like the above would give a better outcome to the average user.  Afterwards, they could change that selection.

In addition, the UI could keep track of such selections and ask the user whether they want to remember that ordering preference.  In my first example, when I choose org.restlet.data.Resource, it could ask (or have a checkbox) to remember that choice and then the next time the org.restlet.data.Resource class would come up first.  It should still present the options via the same interface but just the selected class would be different.

It might be a good idea to keep the list of possible classes sorted lexicographically and then just use the rules to determine which should be selected by default.

I use the "fix imports" feature all the time and this would be a big time-saving improvement for me.