Bad practice to have two classes of the same name in different packages?

Question

We have split our application so that package A handles data from one external source and package B from another. In both cases we need to create a domain object and have a

Answer 1

Not really poor practice, as in many domains have similar terminology, so you will end-up having same names. On the other hand if both are in same domain, but simply different implementations, you can (somehow) indicate the implementation specifics in the name.
The very ugly thing would be if you have to use both in same source file, in this case you have to use fully qualified name for at least one.

Examples:

java.util.List java.awt.List

indicate implementation in the name:
java.util.ArrayList
java.util.LinkedList