Paul, When two or more types have the same simple name, IntelliJ could simply leave the type references as fully qualified names. For extra credit, it could let the user choose one of the types to be known by its simple name, but this might not be worth the effort. /Jim
"Paul Ruane" <[EMAIL PROTECTED]> wrote in message news:[EMAIL PROTECTED]... > > I guess the only complication would be the logic determining what happens when identically named classes are involved. > > If one is imported and the other is fully qualified, then there is no problem, we leave the two classes as they are. > If both are fully qualified, should IDEA import the first or the most frequently used or should neither be imported? > > Paul. > > > > > "Jim White" > <[EMAIL PROTECTED]> To: [EMAIL PROTECTED] > Sent by: cc: > [EMAIL PROTECTED] Subject: [Eap-features] Forcing the Use of Import Statements > tbrains.com > > > 18/09/2002 17:34 > Please respond to > eap-features > > > > > > > I'm looking for a way to eliminate fully qualified type names from a > body of source code by forcing the code to use import statements. > I was surprised when I realized that IntelliJ's optimize-imports > command doesn't do this. The inspect-code command doesn't do > it either. Is this feature planned for IntelliJ? Thanks. /Jim White > > > _______________________________________________ > Eap-features mailing list > [EMAIL PROTECTED] > http://lists.jetbrains.com/mailman/listinfo/eap-features > > > > > > -- > > This e-mail may contain confidential and/or privileged information. If you are not the intended recipient (or have received this e-mail in error) please notify the sender immediately and destroy this e-mail. Any unauthorized copying, disclosure or distribution of the material in this e-mail is strictly forbidden. > > _______________________________________________ Eap-features mailing list [EMAIL PROTECTED] http://lists.jetbrains.com/mailman/listinfo/eap-features
