title: Bad practice to have two classes of the same name in different packages?
body: <p>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 "Transformer" to do this.</p>
  
  <p>So I have <code>com.foo.bar.a.ThingTransformer</code> and <code>com.foo.bar.b.ThingTransformer</code></p>
  
  <p>I suspect that this is poor practice, but want to see what the good people of SO think.</p>