Tim Funk wrote:
In case you weren't joking ...

It can easily break compatibility if someone introduces a new class with the same class name as another class in a different package.

ex:
import foo.*; /* has class A */
import bar.*; /* has class B */

class Foo {
A a;
B b;
}

Imagine time going by and another developer creates another class called A in the bar package. The code above will not recompile because of the abiguous class name.
I think costin is speaking about importing java.io.*
or org.apache.*.

BTW, there is ant task, for example CheckStyle (http://checkstyle.sourceforge.net/) which could be used
and which may be integrated in build/gump to clean code....




--
To unsubscribe, e-mail: <mailto:tomcat-dev-unsubscribe@;jakarta.apache.org>
For additional commands, e-mail: <mailto:tomcat-dev-help@;jakarta.apache.org>



Reply via email to