You could import as much as possible but still leave ambiguous classes fully-qualified:
import java.sql.date; //... Date sqlDate = new Date(new java.util.Date().getTime()); (or just use a Calendar...) Cheers, Dan -----Original Message----- From: dimiter [mailto:[EMAIL PROTECTED]] Sent: 17 July 2002 11:39 To: [EMAIL PROTECTED] Subject: [Eap-features] Re: Code style - optimize imports... what about: java.sql.Date sqlDate = new java.sql.Date(new java.util.Date().getTime()); "Igor Karpov" <[EMAIL PROTECTED]> wrote in message news:[EMAIL PROTECTED]... > There is an "optimize imports" functionality that is fine, but what I need is > to convert existing code that uses fully-qualified names for no real reason to > the code with the corresponding import statement and ususal plain names. > > Example > > // Before > > com.abc.Type1 doSomething1() {...} > com.abc.Type2 doSomething2() {...} > com.abc.Type1 doSomething2() {...} > com.abc.Type2 doSomething4() {...} > // a lot.. > > // After > > import com.abc.Type1; > import com.abc.Type2; > > Type1 doSomething1() {...} > Type2 doSomething2() {...} > Type1 doSomething2() {...} > Type2 doSomething4() {...} > > So it is the import optimization, isn't it? Would be nice if IDEA supported it. > > > ------------------------------------ > Mail.Ru - ������, ��������, �������! > ------------------------------------ _______________________________________________ Eap-features mailing list [EMAIL PROTECTED] http://lists.jetbrains.com/mailman/listinfo/eap-features _______________________________________________ Eap-features mailing list [EMAIL PROTECTED] http://lists.jetbrains.com/mailman/listinfo/eap-features
