android - Fail-safe strategy/best practice for AAR dependency -


i relatively new android programming. have read books , posts online trying figure out fail-safe strategy handle aar dependency issue, none of them gave me satisfactory answers.

we trying develop aar , plan distribute 3rd-party android developers. our aar depends on number of external libs, , 3rd-party developers' projects might use of libs well. not sure how handle of issues arise such transitive dependency scenario.

for example, our aar depends on lib of version 1.0. , 3rd-party developer's project depends on lib of version 0.9. when starts use our aar, seems has upgrade 1.0 in order our aar function properly. if 3rd-party dev doesn't have "luxury" upgrade @ will? similar issue exists in other way around, is, 3rd-party developer uses higher version of lib our aar.

does such fail-safe strategy exist enable our 3rd-party developers blindly drop our aar projects , works? if not, what's best practice build/distribute our aar, minimal disruption caused on 3rd-party developers' side?

we use android studio/gradle our build process.


Comments

Popular posts from this blog

java - Jasper subreport showing only one entry from the JSON data source when embedded in the Title band -

serialization - Convert Any type in scala to Array[Byte] and back -

SonarQube Plugin for Jenkins does not find SonarQube Scanner executable -