title: Android Studio: “new module -> import existing project” vs. “import module”
body: <h1>What I have:</h1>
  
  <p>Four independently working Android modules:</p>
  
  <ol>
  <li><p><code>MyProjectMainModule</code>, a main container application, attached to <code>MyProject</code></p></li>
  <li><p><code>MyGradleModule</code>, a library, with all necessary components built during <code>gradlew</code> process. </p></li>
  <li><p><code>MyPreGradleModule</code>, a library, with <code>src/</code>, <code>res/</code>, <code>AndroidManifest.xml</code>, and <code>pom.xml</code>, without gradle wrapper</p></li>
  <li><p><code>MyRawModule</code>, a library, with <code>src/</code>, <code>res/</code>, <code>AndroidManifest.xml</code>, without <code>pom.xml</code> (commonly seen in Ant-based Eclipse projects)</p></li>
  </ol>
  
  <h1>What I'd like to achieve:</h1>
  
  <p>To import all three modules (i.e. <code>MyGradleModule</code>, <code>MyPreGradleModule</code>, <code>MyRawModule</code>) into <code>MyProject</code> as dependencies of <code>MyProject</code>. The complete project structure should resemble below project structure:</p>
  
  <pre><code>MyProject
  |--MyProjectMainModule
  |--MyGradleModule
  |--MyPreGradleModule
  |--MyRawModule
  </code></pre>
  
  <h1>Question:</h1>
  
  <p>Realizing all three modules (<code>MyGradleModule</code>, <code>MyPreGradleModule</code>, and <code>MyRawModule</code>) have different structures, what are the most optimal ways to import each modules with minimal efforts?</p>
  
  <p>Could you please match one of the following Android Studio menu items with each modules in your answer (if you use any): </p>
  
  <ol>
  <li><code>File</code> -> <code>Import Module...</code></li>
  <li><code>File</code> -> <code>New Module...</code> -> <code>Import Existing Project</code></li>
  <li><code>File</code> -> <code>New Module...</code> -> <code>Android Library</code></li>
  </ol>