Joachim Sauer wrote: > When a class in the package com.foo.bar imports com.foo.bar.Baz this > import is not unused, but unnecessary, would it be possible to > (optionally) mark this as a warning?
I believe that this type of import can be used when Baz itself is ambiguous. For example: import java.awt.*; import java.util.*; // Now "List" is ambiguous since it exists in two packages import java.util.List; // Now "List" unambiguously means java.util.List If you warn against this, people should be aware that the import could be there on purpose. Removing the import can potentially make the code uncompilable, in this version or in future versions of APIs where new classes are introduced. _______________________________________________ Eap-features mailing list [EMAIL PROTECTED] http://lists.jetbrains.com/mailman/listinfo/eap-features
