[izpack-devel] OT: Java Imports in IzPack

[Aaron Mulder]

I think it was more important before the age of IDEs where you could
(something)-click on a class name and have it take you to the class,
or pop up JavaDoc, or whatever.  Back in the dark ages, if you saw a
class called Foo used in the code, and all the imports were *, it was
darned irritating to try to figure out what Foo actually was and where
it came from and how to find some documentation on it.

Now that the IDEs have caught up, I think this "best practice" is
mostly unnecessary, but it's still kind of a convention so what can
you do?  As Julien mentioned, write them however you want and let your
IDE clean up after you.  :)

Thanks,
    Aaron

On 3/12/06, Julien Ponge <julien at izforge.com> wrote:
> Explicit imports are indeed recommended in most best practices. The
> thing is that you can always start with a star import, and ask your
> favorite IDE to replace it with only the required imports. Except
> that it makes your dependencies explicit, I think I read once that it
> speeds-up the compilation, but I am really not sure that (1) it is
> significant, and (2) that it is actually the case :-)
>
> --
> Julien Ponge
> http://www.izforge.com/
> GnuPG ID: 0xCD9DE030
>
>
>
> _______________________________________________
> izpack-devel mailing list
> izpack-devel at lists.berlios.de
> http://lists.berlios.de/mailman/listinfo/izpack-devel
>