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

Nothing wrong with that, since it's very unlikely you'll use both classes together in the same code. Duplicating the a/b distinction from the package in all class names would be worse.