title: Tips on debugging Maven dependency issues
body: <p>We use Maven in the large corporate IT shop I work. The dependency hierarchy seems to become unmanageable very quickly even if I just need to add one new dependency. On small changes to the code base I find I spend more time debugging Maven problems then the actual code. I am looking for some direction on how to </p>
  
  <ol>
  <li>more quickly debug the issues</li>
  <li>How to design new software to avoid the tangled web of circular dependencies, putting exclusions in pom.xml, etc....</li>
  </ol>
  
  <p>Thanks!</p>