title: Eclipse can't resolve transitive dependency projects?
body: <p>In a Java project in Eclipse, I am trying to debug project A.</p>
  
  <p>Project <code>A</code> has a dependency on <code>B.jar</code>, normally <code>B.jar</code> comes from my <code>.m2/repository</code>.
  but now I want to make some temp changes to <code>B</code>'s code, and have it reflected in <code>A</code>,
  so I directly edit the source code in <code>B</code> project in eclipse, and set <code>B</code> as a dependency project in <code>A</code>'s build path. Additionally, both <code>A</code> and <code>B</code> refer to <code>C.jar</code> as their dependencies.</p>
  
  <p>This builds <code>A</code> fine, but when it is run, <code>A</code>'s <code>classpath</code> contains 2 copies of all the classes and resources in <code>C.jar</code>. this creates a problem for those hibernate <code>hbm.xml</code> mapping files in <code>C.jar</code> and I got errors saying <code>duplicate mapping for...</code></p>
  
  <p>This looks to be a defect in eclipse, in that it lacks the resolution ability as maven posseses. is there a way to work around this? (apart from building B and installing to .m2 instead of having it as a dependency project)</p>
  
  <p>Thanks</p>