You can add this task: task copyLibs(type: Copy) { from configurations.compile into ‘libs’ } Dependencies will be downloaded from your Nexus, but when you need package the library, execute this task first and jar files will be copied and included inside final aar.
You put your flatDir block in the wrong repostories block. The repositories block inside buildscript tells Gradle where to find the Android-Gradle plugin, but not the rest of the dependencies. You need to have another top-level repositories block like this: repositories { mavenCentral() flatDir { dirs ‘aars’ } } I tested this and it works … Read more
AAR files are more similar to Jars than to Dlls for the following reason: Dlls can be shared across applications where as AARs and jars are packaged in with your app. AARs vs Jars: The main difference between a Jar and a AAR is that AARs include resources such as layouts, drawables etc. This makes … Read more
While I haven’t tried uploading the artifacts with a deployment to Sonatype (or even a local repo), here’s what I managed to come up with a few weeks ago when trying to tackle the same problem. android.libraryVariants.all { variant -> def name = variant.buildType.name if (name.equals(com.android.builder.core.BuilderConstants.DEBUG)) { return; // Skip debug builds. } def task … Read more
I have solved my problem by setting transitive attribute for my aar dependency: compile (‘com.somepackage:LIBRARY_NAME:1.0.0@aar’){ transitive=true }
The aar file doesn’t contain the nested (or transitive) dependencies and doesn’t have a pom file which describes the dependencies used by the library. It means that, if you are importing a aar file using a flatDir repo you have to specify the dependencies also in your project. In your case adding transitive=true doesn’t resolve … Read more
The AAR file consists of a JAR file and some resource files (it is basically a standard zip file with a custom file extension). Here are the steps to convert: Extract the AAR file using standard zip extract (rename it to *.zip to make it easier) Find the classes.jar file in the extracted files Rename … Read more
If your library is set up as an Android library (i.e. it uses the apply plugin: ‘com.android.library’ statement in its build.gradle file), it will output an .aar when it’s built. It will show up in the build/outputs/aar/ directory in your module’s directory. You can choose the “Android Library” type in File > New Module to … Read more
Building upon Josiah’s answer, here’s how I got it to work. Following his instructions (under edit) (File -> New-> New Module -> Import .JAR/.AAR) and import your .AAR. Then in your project build.gradle (not the top level one, the one under ‘app’) add the following (in the dependencies section): dependencies { compile project(‘:Name-Of-Your-Project’) } Note … Read more