Then reference it from your gradle build. But what if that's not an option, for example if the library you're referencing is in development?Ī simple and extremely straightforward option is to create a local maven repository on your dev machine, and install your library in there. aar package it it would have to ideally be stored in the central maven repository (now that maven central finally supports android archive packages!). This means that to add a reference to an. I want to look at either detecting issues or putting huge warnings. Using aar files locally can be dangerous. As explained by +Xavier Ducrichet in this comment: aar packages locally doesn't work very well, and it seems like that's by design. But what if you want to decouple the library, keep it separate so that you can use it in other projects or share it with the community? The Gradle build system will package it as an android archive package (.aar) and you can add that as a dependency to your projects. Unfortunately, since the new build system is quite fresh (version 0.4.2 at the moment), the documentation is rather limited, so not everything is clear and simple.įor example, if you have a solution with an android library and an android app (that depends on the library), your build will work just fine. The new build system comes with a number of great features like multi project builds, android archive packages (.aar) for android libraries and so on. Since Gradle became the new build system for Android there were a lot of questions popping up all over the net about how to use it. aar Android library packages in gradle builds

Add aar do gradle android studio