定义多个 Maven 存储库时的 Gradle 传递依赖解决问题

Question

在我的 gradle 文件中存在多个 maven 存储库时，我遇到了关于解决传递依赖的问题。这是我的根目录和模块 gradle 文件的快照 -

根目录-

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

        maven {
            name 'B'
            url 'someUrl2'

            credentials {
                //
            }
        }

}

模块级 gradle -

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 sync/build 时，gradle 都会尝试从 Repo 'B' 获取上述依赖项的一些传递依赖项的 maven-metadata 文件。所有依赖项都存在于 Repo 'A' 中。我不确定为什么即使“A”列在“B”上方，也会在仓库“B”中搜索 maven-metadata。

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

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

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

我不确定为什么 POM 文件中存在特定版本依赖会导致此问题。

下面是 gradle 调试日志的 sn-p -

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 会将检索到的信息缓存到本地，以提高后续构建的性能。