title: Finding out all conflicting packages/classes of referenced jars in an Eclipse project
body: <p>I am currently dealing with a huge Eclipse project (not written by me). This project doesn't use any dependency management tools. It references hundreds of JARs.</p>
  
  <p>Some of these JARs contain same packages (and classes), but in different versions. Currently, resolving conflicts works by manually (and randomly!) reordering these JARs in <code>Order&amp;Export</code> (in Project Properties).</p>
  
  <p>This was done for a long time now, and there are now lots of packages/classes with different vendors/versions/product-lines.</p>
  
  <p>Reordering causes some parts of the project to fail while other parts start working, and oppositely.
  Strangely, lots of orders do <em>not</em> cause build errors, but only runtime errors.</p>
  
  <p><strong>Can this mess be solved by an tool, which would suggest certain automatic order of dependent JARs?</strong></p>