定义多个Maven repos时，级别传递依赖解决问题

Question

在我的gradle文件中存在多个maven repos的情况下，我遇到了一个关于解决传递依赖的问题。以下是我的根级和模块级文件的快照-

根级-

allprojects {
repositories {
        maven {
            name 'A'
            url 'someUrl1'
            credentials {
             //
            }
        }

        maven {
            name 'B'
            url 'someUrl2'

            credentials {
                //
            }
        }

}

模块级分级-

dependencies {
implementation fileTree(dir: 'libs', include: ['*.jar'])
compile 'com.google.android.gms:play-services-analytics:11.0.4'
compile 'com.google.android.gms:play-services-auth:11.0.4'
compile 'com.google.android.gms:play-services-gcm:11.0.4'
compile 'com.google.android.gms:play-services-location:11.0.4'
compile 'com.google.android.gms:play-services-maps:11.0.4'

}

我遇到的问题是，每次执行gradle同步/构建时，gradle都会尝试从Repo 'B‘获取上述依赖项的一些传递依赖项的maven-元数据文件。所有依赖项都存在于回购'A‘中。我不知道为什么回购'B‘是搜索maven元数据，即使'A’列在'B‘之上。

奇怪的是，它不会导致任何构建失败，因为它最终会从本地gradle缓存中获取依赖项，但是它会显著增加我的构建时间，因为它在每次构建过程中进行多个网络调用。

我注意到的一件事是，11.0.4版本的gms库使用方括号，即11.0.4来提及POM文件中它们依赖项的版本。

为了解决这个问题，我将依赖项更新为11.8.0，其中POM文件没有使用方括号来提及它们的依赖版本，问题就消失了。

我不知道为什么POM文件中存在特定的版本依赖性会导致这个问题。

下面是gradle调试日志的片段-

23:24:26.977 [DEBUG] [org.gradle.api.internal.artifacts.ivyservice.resolveengine.graph.builder.DependencyGraphBuilder] Visiting configuration com.google.android.gms:play-services-analytics:11.0.4(default).
23:24:26.978 [DEBUG] [org.gradle.api.internal.artifacts.ivyservice.ivyresolve.DynamicVersionResolver] Attempting to resolve version for com.google.android.gms:play-services-analytics-impl:[11.0.4] using repositories [C:\Users\abc\AppData\Local\Android\Sdk\extras\m2repository, C:\Users\abc\AppData\Local\Android\Sdk\extras\google\m2repository, C:\Users\abc\AppData\Local\Android\Sdk\extras\android\m2repository, maven, maven2]
23:24:26.978 [DEBUG] [org.gradle.api.internal.artifacts.repositories.resolver.ResourceVersionLister] Listing all in file:/C:/Users/abc/AppData/Local/Android/sdk/extras/m2repository/com/google/android/gms/play-services-analytics-impl/[revision]/play-services-analytics-impl-[revision].pom
23:24:26.978 [DEBUG] [org.gradle.api.internal.artifacts.repositories.resolver.ResourceVersionLister] using org.gradle.internal.resource.local.FileResourceConnector@24522fcd to list all in file:/C:/Users/abc/AppData/Local/Android/sdk/extras/m2repository/com/google/android/gms/play-services-analytics-impl/
23:24:26.978 [DEBUG] [org.gradle.api.internal.artifacts.repositories.resolver.MavenMetadataLoader] parsing maven-metadata: C:\Users\abc\AppData\Local\Android\sdk\extras\google\m2repository\com\google\android\gms\play-services-analytics-impl\maven-metadata.xml
23:24:26.980 [DEBUG] [org.gradle.api.internal.artifacts.repositories.resolver.DefaultExternalResourceArtifactResolver] Loading file:/C:/Users/abc/AppData/Local/Android/sdk/extras/google/m2repository/com/google/android/gms/play-services-analytics-impl/11.0.4/play-services-analytics-impl-11.0.4.pom
23:24:26.983 [DEBUG] [org.gradle.api.internal.artifacts.repositories.resolver.ExternalResourceResolver] Metadata file found for module 'com.google.android.gms:play-services-analytics-impl:11.0.4' in repository 'C:\Users\abc\AppData\Local\Android\Sdk\extras\google\m2repository'.
23:24:26.983 [DEBUG] [org.gradle.api.internal.artifacts.repositories.resolver.ResourceVersionLister] Listing all in file:/C:/Users/abc/AppData/Local/Android/sdk/extras/android/m2repository/com/google/android/gms/play-services-analytics-impl/[revision]/play-services-analytics-impl-[revision].pom
23:24:26.983 [DEBUG] [org.gradle.api.internal.artifacts.repositories.resolver.ResourceVersionLister] using org.gradle.internal.resource.local.FileResourceConnector@24522fcd to list all in file:/C:/Users/abc/AppData/Local/Android/sdk/extras/android/m2repository/com/google/android/gms/play-services-analytics-impl/
23:24:26.984 [INFO] [org.gradle.cache.internal.DefaultCacheAccess] Creating new cache for metadata-2.36/module-versions, path C:\Users\abc\.gradle\caches\modules-2\metadata-2.36\module-versions.bin, access org.gradle.cache.internal.DefaultCacheAccess@334c9d50
23:24:26.984 [DEBUG] [org.gradle.cache.internal.LockOnDemandCrossProcessCacheAccess] Acquiring file lock for artifact cache (C:\Users\abc\.gradle\caches\modules-2)
23:24:26.989 [DEBUG] [org.gradle.cache.internal.DefaultFileLockManager] Waiting to acquire exclusive lock on artifact cache (C:\Users\primanda\.gradle\caches\modules-2).
23:24:26.990 [DEBUG] [org.gradle.cache.internal.DefaultFileLockManager] The file lock is held by a different Gradle process (pid: 14924, lockId: -9157439162897582946). Pinged owner at port 56301
23:24:26.990 [DEBUG] [org.gradle.cache.internal.locklistener.DefaultFileLockContentionHandler] Gradle process at port 56301 confirmed unlock request for lock with id -9157439162897582946.
23:24:26.990 [DEBUG] [org.gradle.cache.internal.locklistener.DefaultFileLockContentionHandler] Gradle process at port 56301 confirmed unlock request for lock with id -9157439162897582946.
23:24:27.001 [DEBUG] [org.gradle.cache.internal.DefaultFileLockManager] Lock acquired on artifact cache (C:\Users\abc\.gradle\caches\modules-2).
23:24:27.001 [DEBUG] [org.gradle.cache.internal.btree.BTreePersistentIndexedCache] Opening cache module-versions.bin (C:\Users\abc\.gradle\caches\modules-2\metadata-2.36\module-versions.bin)
23:24:27.002 [DEBUG] [org.gradle.cache.internal.btree.BTreePersistentIndexedCache] Opening cache module-metadata.bin (C:\Users\abc\.gradle\caches\modules-2\metadata-2.36\module-metadata.bin)
23:24:27.004 [DEBUG] [org.gradle.api.internal.artifacts.ivyservice.ivyresolve.CachingModuleComponentRepository] Using cached module metadata for module 'com.google.android.gms:play-services-analytics-impl:11.0.4' in 'maven'
23:24:27.004 [DEBUG] [org.gradle.internal.resource.transfer.DefaultCacheAwareExternalResourceAccessor] Constructing external resource: https://someurl2/com/google/android/gms/play-services-analytics-impl/maven-metadata.xml

Answer 1

这个问题确实是由符号[11.0.4]引起的，它将Gradle解释为一个范围，从而触发动态版本解析。

在执行动态版本解析时，Gradle将搜索构建脚本中定义的所有存储库，以确保对所有可用版本有一个完整的视图。然后，Gradle将在本地缓存检索到的信息，以提高后续构建的性能。