title: Eclipse gradle and maven tooling - local resolution
body: <p>I want to gradually migrate a multi-module maven build to a multi-module gradle build.</p>
  
  <p>I'm currently using <a href="http://eclipse.org/m2e/" rel="nofollow">m2e</a> maven tooling in eclipse and one feature I like is that if projectA depends on projectB and both projects are in my eclipse workspace, m2e is smart enough to use the local .class files for projectB instead of using the .jar file from my maven repository. Let's call this feature "local resolution".</p>
  
  <p>So, can the eclipse gradle tooling and <a href="http://eclipse.org/m2e/" rel="nofollow">m2e</a> play nicely together?</p>
  
  <ol>
  <li>If a gradle project depends on a maven project, can the maven project be locally resolved</li>
  <li>If a maven project depends on a gradle project, can the gradle project be locally resolved</li>
  <li>If a gradle project depends on a gradle project, can the dependent gradle project be locally resolved?</li>
  </ol>