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

It's fine. This is precisely why, by design, different packages have different namespaces.