title: Instruct Maven to use Ivy's generated classpath
body: <p>We are adding new code to an existing project that uses a custom build system developed with <strong>Ant</strong> and <strong>Ivy</strong> for dependency management.</p>
  
  <p>Our new team is used to <strong>Maven</strong> and its features like testing execution, cobertura reports, etc.</p>
  
  <p>Our question is: is it viable to add a pom.xml matching the current project structure, but instruct Maven to load its classpath from the "lib" dir already filled by Ivy?
  In other words: we want to use Maven without its dependency management. </p>
  
  <p>One <em>really dirty</em> approach would be to generate one big jar from the libdir and config the pom.xml to include just that... but we believe there should be cleaner approach.</p>
  
  <p>Any idea or recommendation?</p>
  
  <p>Note: we are not interested in generating a pom.xml with dependencies from the Ivy config, we just want Maven to rely on Ivy's generated classpath. No need to discriminate between test/runtime/compile classpath.</p>