【maven】maven包冲突处理笔记

项目场景：

在日常维护的时候升级了兄弟部门提供的api包版本，启动应用的时候报错

---

问题描述

应用打包 mvn clean install -Dmaven.test.skip=true 通过。本地启动时报错

***************************
APPLICATION FAILED TO START
***************************

Description:

An attempt was made to call a method that does not exist. The attempt was made from the following location:

    javax.el.ELManager.getExpressionFactory(ELManager.java:38)

The following method did not exist:

    javax.el.ELUtil.getExpressionFactory()Ljavax/el/ExpressionFactory;

The method's class, javax.el.ELUtil, is available from the following locations:

    jar:file:/C:/apache-maven-3.8.1/repo/javax/el/javax.el-api/2.2.4/javax.el-api-2.2.4.jar!/javax/el/ELUtil.class
    jar:file:/C:/apache-maven-3.8.1/repo/org/glassfish/jakarta.el/3.0.3/jakarta.el-3.0.3.jar!/javax/el/ELUtil.class

The class hierarchy was loaded from the following locations:

    javax.el.ELUtil: file:/C:/apache-maven-3.8.1/repo/javax/el/javax.el-api/2.2.4/javax.el-api-2.2.4.jar


Action:

Correct the classpath of your application so that it contains a single, compatible version of javax.el.ELUtil

---

原因分析：

其实这个报错非常清晰，javax.el.ELUtil这个类分别存在于包javax.el-api和jakarta.el包中，常规的解决办法就是找到对应的包引用，以及相关的代码引用，然后保证项目只引用正确的那个包。

---

解决方案：

那么怎么找到包的引用呢？maven为我们提供了一个命令

mvn dependency:tree -D outputFile=dependency.txt

其中mvn dependency:tree 的含义是把项目中maven的依赖关系打印成一个树形结构；outputFile=dependency.txt是把树形结构的文本打印到dependency.txt这个文件中方便查看。

最终根据打印的结构树理清依赖关系，通过调整，让应用只依赖一个jar包，项目启动成功