I think that this is still a bug. Importing a class is a textual action: there can't be any difference between importing java.sql.SQLException and java.sql.SQLException, even if the two classes are derrived from different source paths etc. I think IDEA should remove duplicates from the Auto-Import popup completion menu (and probably all others).
The only advantage I can see to having both listed is as a warning that your classpath may be setup wrong, and there are probably more direct ways for IDEA to warn you of that. On Sat, 8 Jun 2002, Vladimir Korenev wrote: > I have found that there was path to sources from Sun JDK 1.3.0 in "Sources" > page of IBM JDK 1.3.0 properties. I removed it and the second problem > disappeared. > > The first problem seems to disappear too. Sorry to trouble you. > > "Vladimir Korenev" <[EMAIL PROTECTED]> wrote: > > > > This error occures irregulary but often. When I tried to make a > > short example, I was not able to reproduce the bug. I have noticed > > that the only exception that causes error is SQLException. Maybe > > other core java exceptions behaves the same way, but they are not > > met so frequently in my current project. > > > > There is another strange thing with core java classes. They appear > > twice in the list (see attachment). I use IBM 1.3.0 as target JDK > > and rt.jar is found only once in JDK the "Classpath" page of > > "Configure JDKs" window. [Picture of import menu showing only java.sql.SQLException twice.] _______________________________________________ Eap-bugs mailing list [EMAIL PROTECTED] http://lists.jetbrains.com/mailman/listinfo/eap-bugs
