http://java.sun.com/j2se/1.5.0/docs/guide/language/static-import.html
http://java.sun.com/developer/jdctechtips/2004/tt1005.html
The following are recommendations for a good use of Static Import:?! So when should you use static import Very sparingly Only use it when you'd otherwise be tempted to declare local copies of constants, or to abuse inheritance (the Constant Interface Antipattern) . In other words, use it when you require frequent access to static members from one or two classes. If you overuse the static import feature, it can make your program unreadable and unmaintainable, polluting its namespace with all the static members you import. Readers . of your code (including you, a few months after you wrote it) will not know which class a static member comes from Importing all of the static members from a class can be particularly harmful to readability; if you need only one or two members Import Themby, Static Import Can make your program more readable, by removing the boilerplate of review of class names.
