I created an Android library (called MyLib) which depends on other library available on maven repo (like gson, retrofit, etc.).
MyLib
|
|-- Retrofit
|-- Gson
|-- ...
MyLib is packaged to an aar
file.
The goal is to publish an aar library which can be included into an Android app (called MyApp) without specifying a second time the dependencies that MyLib uses.
MyApp
|
|-- MyLib
| |-- Retrofit
| |-- gson
| |-- ...
This is my build.gradle file for MyLib
dependencies {
compile fileTree(dir: 'libs', include: ['*.jar'])
compile 'com.squareup.retrofit:retrofit:1.9.0'
compile 'com.google.code.gson:gson:2.3.1'
}
Now, if I want to build and run MyApp without dependency issue, I had to use the following build.gradle for MyApp (if I don't specify retrofit and gson as deps, a runtime exception is thrown because the deps are not available).
dependencies {
compile('MyLib@aar')
compile 'com.squareup.retrofit:retrofit:1.9.0'
compile 'com.google.code.gson:gson:2.3.1'
}
I don't want to specify in MyApp the dependencies that are used inside MyLib, How should I write my build.gradle files?
Thansk in advance
When publishing an
aar
to a maven repository (local or remote) and including it usingcompile (...@aar)
transitive dependencies are turned off.To enable transitive dependencies for an
aar
library:You can read more about this here:
Can an AAR include transitive dependencies?
This works with
aar
libraries that are published to a remote or local maven repository, In your case it sounds like the library will not be published to even a local maven repository. I can't find any definitive information as to if it will work in your circumstances, but you should give it a shot.