Supposing you have mylib.aar in your current directory, try the following: $ unzip myLib.aar -d tempFolder # or other extracting tool # Change whatever you need $ jar cvf myNewLib.aar -C tempFolder/ .
1. Publishing In your aar project, add maven-publish plugin and add necessary plugin configuration. apply plugin: ‘com.android.library’ apply plugin: ‘maven-publish’ … dependencies { testCompile ‘junit:junit:4.12’ compile ‘com.android.support:appcompat-v7:23.1.1’ compile ‘com.novoda:bintray-release:0.2.7’ } … publishing { publications { maven(MavenPublication) { groupId ‘com.example’ //You can either define these here or get them from project conf elsewhere artifactId ‘example’ version … Read more
According to Xavier Durochet’s explanation on G+, it’s due to one of the libraries you use having it’s own ic_launcher.png — which they of course should not (more on that at the bottom). Chances are the two icons mentioned in the log are different: one is yours and another one is most likely the generic … Read more
Here’s what I’ve done to use a gradle reference with a Cordova plugin, I think this might help you. Global structure : pluginFolder/ build-extras.gradle plugin.xml yourDirContainingYourAAR/ src/ android/ yourFile.gradle myPlugin.java Put your library, say foo.aar, in the yourDirContainingYourAAR directory (create it if needed) In the plugin.xml file : <platform name=”android”> <!– your configuration elements, references, … Read more
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
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
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 }