+1 Any ambiguity would be left untouched as in dimiter's example: java.sql.Date sqlDate = new java.sql.Date(new java.util.Date().getTime()); It could be even fancy enough to ask which declaration should be in the import section but "Do not harm" would be enough.
BTW this is very useful when you have some code that has been generated and the generator has gone the easy way (and obviously when your generator is your sub-standard developer... ;-O ) Jacques "Pavel Bernshtam" <[EMAIL PROTECTED]> wrote in message ah3f4f$6dj$[EMAIL PROTECTED]">news:ah3f4f$6dj$[EMAIL PROTECTED]... > +5 > > I already asked it! > > "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
