I have a project with several *Dependencies.xml
files which the Unity Jar Resolver resolves fetching the .aar files and storing them on Plugins/Android.
When installing Ironsource, I saw in the documentation that it says to add the dependencies to the mainTemplate.gradle file:
dependencies {
// Your other dependencies //
compile fileTree(dir: 'libs', include: ['*.jar'])
compile 'com.google.android.gms:play-services-ads-identifier:16.0.0'
compile 'com.android.support:support-v4:27.1.1'
**DEPS**
// Your other dependencies //
// ... //
// AdMob's dependency //
compile 'com.google.android.gms:play-services-ads:17.1.1'
}
Because one of my dependencies that the jar resolver imports is an older version of support-v4 my build fails.
Seeing this new alternative, can I move all the dependencies files to the gradle file and let Gradle auto resolve this problem on the post build process?
Is there any pros/cons that the jar resolver has that Gradle doesn't? For what I know the Jar Resolver uses gradle.