title: How to publish single android AAR dependent on internal modules and 3rd party libs
body: <h2>Problem statement</h2>
  <p>We need to deliver an android SDK in form of single AAR package wherein our code internally divided into various sub-modules and also has dependencies on external libs(AARs). I'm stucked in the way that how to package the modules in such a way that only single AAR is delivered which resolves the dependencies internally. Currently when the SDK code is assembled, it generates an AAR but that AAR doesn't include respective dependent modules and it hardly has a size in few KBs only.</p>
  <h2>Solutions tried</h2>
  <p>I have already explored the way it is achieved like mavenizing the project as mentioned on:
  <a href="https://www.survivingwithandroid.com/2014/05/android-guide-to-publish-aar-to-maven-gradle.html" rel="nofollow noreferrer">https://www.survivingwithandroid.com/2014/05/android-guide-to-publish-aar-to-maven-gradle.html</a>
  <a href="https://stackoverflow.com/questions/33445270/how-to-include-jar-dependency-into-an-aar-library">How to include JAR dependency into an AAR library</a></p>
  <p>Kindly help to get build as single AAR.</p>