为什么Gradle会降低Grails 3.1应用程序中的传递依赖项的级别？

Question

我的grails-flyway插件的传递性依赖有问题。org.grails.plugins:grails-flyway:0.2.1声明了对org.flywaydb:flyway-core:4.0.1的依赖。当我将插件包含到Grails3.1.6项目中时，Gradle将Flyway降级为3.2.1版本。

+--- org.grails.plugins:grails-flyway:0.2.1
|    \--- org.flywaydb:flyway-core:4.0.1 -> 3.2.1

我的Gradle构建文件如下所示

buildscript {
    ext {
        grailsVersion = project.grailsVersion
    }
    repositories {
        maven { url "https://repo.grails.org/grails/core" }
    }
    dependencies {
        classpath "org.grails:grails-gradle-plugin:$grailsVersion"
        classpath "com.bertramlabs.plugins:asset-pipeline-gradle:${assetPipelinePluginVersion}"
        classpath "org.grails.plugins:hibernate5:5.0.5"
        classpath 'com.github.ben-manes:gradle-versions-plugin:0.12.0'
    }
}

version "0.40.15"
group "zsc.supporter"

apply plugin: "war"
apply plugin: "org.grails.grails-web"
apply plugin: "org.grails.grails-gsp"
apply plugin: "org.grails.grails-doc"
apply plugin: "asset-pipeline"
apply plugin: 'com.github.ben-manes.versions'

ext {
    grailsVersion = project.grailsVersion
    gradleWrapperVersion = project.gradleWrapperVersion
}

repositories {
    maven { url "https://repo.grails.org/grails/core" }
    maven { url "https://dl.bintray.com/saw303/plugins" }
}

dependencyManagement {
    imports {
        mavenBom "org.grails:grails-bom:$grailsVersion"
    }
    applyMavenExclusions false
}

dependencies {
    compile "org.springframework.boot:spring-boot-starter-logging"
    compile "org.springframework.boot:spring-boot-autoconfigure"
    compile "org.grails:grails-core"
    compile "org.springframework.boot:spring-boot-starter-actuator"
    compile "org.springframework.boot:spring-boot-starter-tomcat"
    compile "org.grails:grails-dependencies"
    compile "org.grails:grails-web-boot"
    compile "org.grails.plugins:cache"
    compile "org.grails.plugins:scaffolding"
    compile "org.grails.plugins:hibernate4"
    compile "org.hibernate:hibernate-ehcache"
    console "org.grails:grails-console"
    profile "org.grails.profiles:web:3.1.6"
    runtime "com.bertramlabs.plugins:asset-pipeline-grails:${assetPipelinePluginVersion}"
    runtime "com.h2database:h2"
    testCompile "org.grails:grails-plugin-testing"
    testCompile "org.grails.plugins:geb"
    testRuntime "org.seleniumhq.selenium:selenium-htmlunit-driver:2.52.0"
    testRuntime "net.sourceforge.htmlunit:htmlunit:2.21"

    compile "org.grails.plugins:spring-security-core:3.0.4"
    compile "org.grails.plugins:quartz:2.0.8"
    compile "org.grails.plugins:mail:2.0.0.RC4"
    compile "eu.bitwalker:UserAgentUtils:1.18"
    compile 'org.mnode.ical4j:ical4j:1.0.7'
    compile 'org.grails.plugins:browser-detection:3.1.0'
    compile "com.googlecode.libphonenumber:libphonenumber:7.3.1"
    runtime 'org.grails.plugins:grails-flyway:0.2.1'

    testCompile "org.grails.plugins:grails-wizer:0.3"
    testCompile 'org.grails:grails-datastore-test-support:5.0.5.RELEASE'

    runtime 'mysql:mysql-connector-java:5.1.29'
}

task wrapper(type: Wrapper) {
    gradleVersion = gradleWrapperVersion
}

assets {
    minifyJs = true
    minifyCss = true
}

目前，我不明白为什么Gradle会降低我的暂时性依赖度。有人能提供这个吗？

我知道我可以在我的flyway-core:4.0.1中强制使用build.gradle依赖，但是我想了解降级的原因。

更新-1

当我运行gradle dependencies | grep flyway时，我得到以下输出。

+--- org.grails.plugins:grails-flyway:0.2.1
|    \--- org.flywaydb:flyway-core:4.0.1 -> 3.2.1
+--- org.grails.plugins:grails-flyway:0.2.1
|    \--- org.flywaydb:flyway-core:4.0.1 -> 3.2.1
+--- org.grails.plugins:grails-flyway:0.2.1
|    \--- org.flywaydb:flyway-core:4.0.1 -> 3.2.1
+--- org.grails.plugins:grails-flyway:0.2.1
|    \--- org.flywaydb:flyway-core:4.0.1 -> 3.2.1

请在巴斯丁找到完整的输出。grails-flyway插件及其pom.xml可以在布林上找到。

更新-2

据org.flywaydb:flyway-core:4.0.1报道，我试图强迫Gradle使用Gradles参考。

configurations.all {
    resolutionStrategy.force 'org.flywaydb:flyway-core:4.0.1'
}

这不影响问题。依赖树仍然使用flyway-core的3.2.1版本。

+--- org.grails.plugins:grails-flyway:0.2.1
|    \--- org.flywaydb:flyway-core:4.0.1 -> 3.2.1

更新-3

Gradles dependencyInsight命令

gradle dependencyInsight --dependency flyway-core --configuration runtime

结果：

:dependencyInsight
org.flywaydb:flyway-core:3.2.1 (selected by rule)

org.flywaydb:flyway-core:4.0.1 -> 3.2.1
\--- org.grails.plugins:grails-flyway:0.2.1
     \--- runtime 

(selected by rule)是什么意思？

“解决方案”--或如何围绕工作

我找不到导致Gradle使用flyway-core:3.2.1而不是flyway-core:4.0.1的规则。但我找到了解决问题的方法。

我将以下内容添加到我的build.gradle中，以修改分级runtime解析策略。

configurations.runtime.resolutionStrategy {

    eachDependency { DependencyResolveDetails det ->

        if (det.requested.name == 'flyway-core' && det.requested.group == 'org.flywaydb') {
            det.useVersion(det.requested.version)
        }
    }
}

Answer 1

造成这种情况的原因是spring-boot-dependencies-1.3.3.RELEASE.pom

这迫使天桥版本达到3.2.1。

根据弹簧启动文件，您应该能够在您的build.gradle：ext['flyway.version'] = '4.0.1'中添加这样的一行

Answer 2

转到Gradle缓存文件文件夹：

cd ~/.gradle/caches/modules-2/files-2.1

搜索此版本号：

grep -r "3.2.1" *

您将发现哪个pom文件正在使用此版本，通常在spring-boot-dependencies-x.y.z.RELEASE.pom中是这样的：

<flyway.version>3.2.1</flyway.version>
......
<groupId>org.flywaydb</groupId>
    <artifactId>flyway-core</artifactId>
    <version>${flyway.version}</version>
</dependency>

这意味着，如果使用spring-boot，它将覆盖某些依赖版本。

通过在gradle.properties文件中添加以下行，您可以再次重写它：

flyway.version=4.0.1

我遇到了一个类似的问题，在上面浪费了几个小时。所以我把这个信息留在这里，希望如果你陷入这个问题，这能节省你的时间。