title: Libraries internally being used by my (non-Android) library not getting included in classes.dex
body: <p>This one has me stumped. I'm clearly missing something, but I can't figure out what.</p>
  
  <p>I have a library (not an Android library - just a regular Java library project), which in turn uses other libraries. So, the setup is:</p>
  
  <pre><code>myApi.jar
  
     |
     +-- com/myapi/ ... (.class files here).
     | 
     +-- libs/
          |
          +-- lib1.jar
          +-- lib2.jar
  </code></pre>
  
  <p>Now, when I include <code>myApi.jar</code> in a project in the libs directory of an Android project, like <code>MyAndroidProject/libs</code>, only the <code>com.myapi. ...</code> classes are getting included in the <code>classes.dex</code> file. The classes from the lib1.jar and lib2.jar are not included in classes.dex</p>
  
  <p>The obvious work-around is to remove the lib1.jar and lib2.jar from the myApi.jar file; and instead place them in <code>MyAndroidProject/libs</code> too. However, this means the users of myApi now have to know that there are additional JAR files to be placed on the build path. This is something I am looking to avoid.</p>
  
  <p>So, is there anything special I need to do to include JAR files being used internally by a library JAR in the <code>classes.dex</code> file?</p>