分级管理传递依赖关系

Question

null

null

尝试强制升级的错误日志：“无法解析配置”：reading-condermination-server-quarkus-impl：TestCompileClasspath“的所有文件。

无法解析JUnit：JUnit：4.13。要求方：project：reading-concermination-server-quarkus-impl>找不到满足版本约束的“junit：junit”版本：依赖路径“com.connor：reading-concermination-server-quarkus-impl:1.0.0-snapshot”-->“junit：junit：4.13”约束路径“com.connor：reading-concermination-server-quarkus-impl:1.0.0-snapshot”-->“junit：junit：{严格4.13}”，原因如下：4.13具有assertThrows约束路径“com.connor：

无法解析JUnit：JUnit：{Strict 4.13}.要求方：project：reading-concermination-server-quarkus-impl>找不到满足版本约束的“junit：junit”版本：依赖路径“com.connor：reading-concermination-server-quarkus-impl:1.0.0-snapshot”-->“junit：junit：4.13”约束路径“com.connor：reading-concermination-server-quarkus-impl:1.0.0-snapshot”-->“junit：junit：{严格4.13}”，原因如下：4.13具有assertThrows约束路径“com.connor：

有人能帮助我强制我的项目使用JUnit4.13（或更高）吗？多谢了。

附带说明：我怀疑这可能是maven本机项目的一个问题，因此可能存在传递依赖项的问题（在maven中，没有api vs实现范围）。

Answer 1

<dependency>
    <groupId>junit</groupId>
    <artifactId>junit</artifactId>
    <version>4.12</version>
</dependency>

implementation(platform("..."))

./gradlew :reading-comprehension-server-quarkus-impl:dependencyInsight --dependency junit:junit --configuration testCompileClasspath

> Task :reading-comprehension-server-quarkus-impl:dependencyInsight
junit:junit:4.13
   variant "compile" [
      org.gradle.status              = release (not requested)
      org.gradle.usage               = java-api
      org.gradle.libraryelements     = jar (compatible with: classes)
      org.gradle.category            = library

      Requested attributes not found in the selected variant:
         org.gradle.dependency.bundling = external
         org.gradle.jvm.version         = 11
   ]
   Selection reasons:
      - By constraint
      - By conflict resolution : between versions 4.13 and 4.12

junit:junit:4.13
\--- testCompileClasspath

junit:junit:4.12 -> 4.13
\--- io.quarkus:quarkus-universe-bom:1.7.0.Final
     \--- testCompileClasspath

A web-based, searchable dependency report is available by adding the --scan option.

Deprecated Gradle features were used in this build, making it incompatible with Gradle 7.0.
Use '--warning-mode all' to show the individual deprecation warnings.
See https://docs.gradle.org/6.3/userguide/command_line_interface.html#sec:command_line_warnings

BUILD SUCCESSFUL in 2s
1 actionable task: 1 executed

Selection reasons:
          - By constraint
          - By conflict resolution : between versions 4.13 and 4.12