FYI, Eclipse's "Organize Imports" command greatly simplifies import management. Puts in the imports you need & removes the ones you don't. When it encounters an ambiguous class name, it lets you know up front. No guesswork involved.
Originally posted by Doug Nichols:
At work, they mandate that we use very specific import statements, instead of ones with an asterick at the end. Eg:
Why? Does the compiler use more memory to execute the application if you include the '*'?
Import statements do not use any memory at runtime. I also doubt that there is an significant difference at compile time. The "specific import" statement is considered more clear since it is obvious which classes you are using. It also can help avoid other issues when there are duplicate class names in different packages.