{"id":573,"date":"2019-01-26T08:14:25","date_gmt":"2019-01-26T13:14:25","guid":{"rendered":"http:\/\/jebware.com\/blog\/?p=573"},"modified":"2020-06-05T11:10:01","modified_gmt":"2020-06-05T16:10:01","slug":"save-time-and-reduce-risk-with-gradles-includegroup","status":"publish","type":"post","link":"https:\/\/jebware.com\/blog\/?p=573","title":{"rendered":"Save time and reduce risk with Gradle\u2019s includeGroup"},"content":{"rendered":"

With the recently released version 5.1, Gradle has added a great, subtle new feature that lets you specify which dependencies should be pulled from which repositories.  To explain what this is, let\u2019s start with the default behavior. In your Gradle file, you probably have multiple repositories defined, like this:<\/span><\/p>\n

\"\"<\/a>When Gradle needs to find a dependency, it will search each of those repositories, in the order they are declared.  So when it goes to download, for example, [com.android.support.constraint:constraint-layout:1.1.3], it will first check the Google repo, which has that artifact, so it\u2019s done.  But then let\u2019s say you want RxJava: [io.reactivex.rxjava2:rxjava:2.1.9]. Gradle checks for it in the Google repo, but Google responds with a HTTP 404 error, so Gradle moves on to the next repository, which is JCenter.  And on and on, for each dependency in your build.<\/span><\/p>\n

This can lead to a couple of problems:<\/span><\/p>\n