Transitive dependencies for local aar library

The question:

We’re making some library, basicly for our API, that we would make life easier for our external developers.

So we created new library project and put Retrofit and some other libraries as dependencies.

dependencies {
    compile ''
    compile ''
    compile 'com.squareup.retrofit2:retrofit:2.0.1'
    compile 'com.squareup.retrofit2:converter-gson:2.0.1'
    compile 'com.squareup.okhttp3:okhttp:3.2.0'

Now when we build it, it produces aar file.

But now when we put the aar file to libs directory and set it as dependency, we still have to put the same dependency in user’s build.gradle file, which sucks. It should be taken from the library, right?

repositories {
    flatDir {
        dirs 'libs'

dependencies {
    compile(name: 'ourlibrary', ext: 'aar') {
        transitive = true;

How to make transitive = true work?

The Solutions:

Below are the methods you can try. The first solution is probably the best. Try others if the first one doesn’t work. Senior developers aren’t just copying/pasting – they read the methods carefully & apply them wisely to each case.

Method 1

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 your issue for the reason described above.

You should use a maven repository (you have to publish the library in a private or public maven repo), you will not have the same issue.
In this case, gradle downloads the dependencies using the pom file which will contains the dependencies list.

All methods was sourced from or, is licensed under cc by-sa 2.5, cc by-sa 3.0 and cc by-sa 4.0

Leave a Comment