Maven从曾祖父母那里获取依赖版本，而不是我们父母的依赖关系管理版本 [英] Maven sourcing dependency version from great-grand-parent instead of our parents dependency-management
问题描述
下面显示了我的POM的层次结构.
Below shows the hierarchy of my POMs.
您可以看到我们有一个用于春季启动项目的公司上级绒球.该POM的父级具有spring-boot-starter，并且导入了我们自己的依赖项管理BOM.
You can see that we have a company parent-pom for spring boot projects. This POM has spring-boot-starter as it's parent, and it imports our own dependency-management BOM.
[INFO] --- hierarchy-maven-plugin:1.4:tree (default-cli) @ user-service ---
[INFO] PARENT com.MY_COMPANY.platform:user:3.20.14-SNAPSHOT
[INFO] PARENT com.MY_COMPANY.platform:spring-boot-parent:3.20.12-SNAPSHOT
[INFO] PARENT org.springframework.boot:spring-boot-starter-parent:1.5.12.RELEASE
[INFO] PARENT org.springframework.boot:spring-boot-dependencies:1.5.12.RELEASE <<<< This pom defines assertJ 2.x
[INFO] [ other imports ]
[INFO] IMPORT com.MY_COMPANY:dependencyManagementBase:2.23.14-SNAPSHOT <<<<<<<<<<<< This pom defines assertJ 3.x
[INFO] IMPORT com.MY_COMPANY.platform:platform-dependency-management:1.20.7
[INFO] ------------------------------------------------------------------------
为了专注于特定内容，我们在依赖关系管理中定义了AssertJ 3；但是，spring-boot-dependencies定义了AssertJ2.与assertJ没什么大不了，但是还有像Mongo-Java-Driver这样的其他鱼没有采用我们的版本.
To focus on a specific, we define AssertJ 3 in our dependency-management; however, spring-boot-dependencies defines AssertJ 2. Not a big deal with assertJ, but there are other fish like Mongo-Java-Driver that are not picking up our version.
Maven在这里如何选择优先级?为什么我们的依存关系管理不能胜过远祖的依存关系管理?
How does Maven choose precedence here? Why doesn't our dependency-management win over a far-ancestor's dependency-management?
我还注意到，如果我将AssertJ添加为MY_COMPANY.platform:spring-boot-parent的依赖项，它也不会在我们的依赖项管理中使用该版本(因此，我暂时将其保留在那里，因此显微镜下的层次较短).
I also noticed that if I add AssertJ as a dependency of MY_COMPANY.platform:spring-boot-parent, it also does NOT use the version in our dependency-management (so I'll just keep it there for now, so the hierarchy under microscope is shorter).
编辑-添加缩写的POM
com.MY_COMPANY.platform:spring-boot-parent
com.MY_COMPANY.platform:spring-boot-parent
<?xml version="1.0" encoding="UTF-8"?>
<project xmlns="http://maven.apache.org/POM/4.0.0" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xsi:schemaLocation="http://maven.apache.org/POM/4.0.0 http://maven.apache.org/xsd/maven-4.0.0.xsd">
<modelVersion>4.0.0</modelVersion>
<groupId>com.MYCOMPANY.platform</groupId>
<artifactId>spring-boot-parent</artifactId>
<version>3.20.12-SNAPSHOT</version>
<packaging>pom</packaging>
<prerequisites>
<maven>3.0.4</maven>
</prerequisites>
<parent>
<groupId>org.springframework.boot</groupId>
<artifactId>spring-boot-starter-parent</artifactId>
<version>1.5.12.RELEASE</version>
</parent>
<properties>
<MYCOMPANYdependencymanagement.version>2.23.13</MYCOMPANYdependencymanagement.version>
</properties>
<dependencies>
<dependency>
<groupId>org.assertj</groupId>
<artifactId>assertj-core</artifactId>
<scope>test</scope>
</dependency>
</dependencies>
<dependencyManagement>
<dependencies>
<dependency>
<groupId>com.MYCOMPANY</groupId>
<artifactId>dependencyManagementBase</artifactId>
<version>${MYCOMPANYdependencymanagement.version}</version>
<type>pom</type>
<scope>import</scope>
</dependency>
</dependencies>
</dependencyManagement>
</project>
com.MY_COMPANY:dependencyManagementBase
com.MY_COMPANY:dependencyManagementBase
<?xml version="1.0" encoding="UTF-8"?>
<project xmlns="http://maven.apache.org/POM/4.0.0" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xsi:schemaLocation="http://maven.apache.org/POM/4.0.0 http://maven.apache.org/xsd/maven-4.0.0.xsd">
<modelVersion>4.0.0</modelVersion>
<groupId>com.MYCOMPANY</groupId>
<artifactId>dependencyManagementBase</artifactId>
<version>2.23.13</version>
<packaging>pom</packaging>
<modules>
<module>spring-dep-man</module>
</modules>
<properties>
<org.assertj-core.version>3.5.2</org.assertj-core.version>
</properties>
<dependencyManagement>
<dependencies>
<dependency>
<groupId>org.assertj</groupId>
<artifactId>assertj-core</artifactId>
<version>${org.assertj-core.version}</version>
<scope>test</scope>
</dependency>
</dependencies>
</dependencyManagement>
</project>
**编辑2-添加显示不同版本的详细层次结构**
**EDIT 2 - Add verbose hierarchy showing different versions **
~/p/springbootparentpom> mvn hierarchy:tree -Dlevel=full
[INFO] --- hierarchy-maven-plugin:1.4:tree (default-cli) @ spring-boot-parent ---
[INFO] Displaying hierarchy.
[INFO] PARENT org.springframework.boot:spring-boot-starter-parent:1.5.12.RELEASE
[INFO] PARENT org.springframework.boot:spring-boot-dependencies:1.5.12.RELEASE
[INFO] DEP_MANAGEMENT ........
[INFO] DEP_MANAGEMENT org.assertj:assertj-core:2.6.0
[INFO] [ ... Many DEP_MAN and IMPORT ... ]
[INFO] IMPORT com.MYCOMPANY:dependencyManagementBase:2.23.14-SNAPSHOT
[INFO] DEP_MANAGEMENT ........
[INFO] DEP_MANAGEMENT org.assertj:assertj-core:3.5.2
[INFO] DEP_MANAGEMENT ........
推荐答案
问题是您的项目不依赖于父项进行依赖项管理，而是依赖于导入的项目. Maven依赖层次结构不能那样工作.最好的解决方案可能是将"parent spring-boot-starter-parent"声明移到MY_COMPANY:dependencyManagementBase项目中.然后，在com.MYCOMPANY.platform中更改父声明，以指向您的dependencyManagementBase项目.这样，您将拥有清晰的继承层次结构.
The issue is that your project is relying not on a parent for dependency management, but on an imported project. The Maven dependency hierarchy doesn't work that way. Probably the best solution would be to move the 'parent spring-boot-starter-parent' declaration into the MY_COMPANY:dependencyManagementBase project. Then change the parent declaration in com.MYCOMPANY.platform to point at your dependencyManagementBase project. That way you would have a clear inheritance hierarchy.
您当前拥有的东西并没有真正使用依赖项管理.也就是说，如果您将dependencyManagementBase项目中的"dependecyManagement"部分更改为"dependency"，则会得到相同的结果.
What you currently have does not really use dependency management. i.e. if you were to change the 'dependecyManagement' section in the dependencyManagementBase project to 'dependency', you would get the same results.
这篇关于Maven从曾祖父母那里获取依赖版本，而不是我们父母的依赖关系管理版本的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！
