Fallback to another repo if first one is incomplete


(Tomáš Procházka) #1

I have one big issue with the gradle, it is caused a little bit by Android Studio developers, but I’m curious what is your opinion on such problem.

One maven dependency can have several variants defined by “classifier”.
When gradle found first repository which contain the pom.xml of my declared dependency it stay with it forever.
Also when I’m using the classifier which is not present in this repository.

Related report in the google bugtracking:
https://code.google.com/p/android/issues/detail?id=221536

They simply put a offline repository integrated to the AS where is one dependency incompleted. Without classifier that exist in maven central repo.

Should gradle automatically look to another repository if something is missing in current one? Especially if it is local repository?

Thanks for reply.