problem description:
as shown in figure:
such a project project, where view edaily-service and edaily-web reference jar version is inconsistent. Take the spring version for example: web is 4.3.29
and service is 4.0.9:
. So when maven USES war, does it use 4.0.9 jar or 4.3.29 jar?
solution:
is based on the version referred to by the maven-compiler-plugin POM file:
<plugin>
<artifactId>maven-compiler-plugin</artifactId>
<configuration>
<source>1.8</source>
<target>1.8</target>
<encoding>UTF-8</encoding>
</configuration>
</plugin>
maven-compiler-plugin is in edaily-web, so it is packaged as version 4.3.29.
Read More:
- Maven compilation error: package does not exist jar package does not exist
- Zip to decompress the jar package, like the add file in the jar package
- Idea Maven project uses package to package and report error (package does not exist)
- Does the version of idea2020.1 import mybayis jar package or report an error? Error: (4,28) Java: package org.apache.ibatis.io does not exist
- Maven’s jar package conflict; Maven’s introduction
- The spring boot project directly replaces the referenced jar package
- Update project manually_ Solution of too large jar package in springboot
- Tomcat was unable to load Maven’s jar package
- How to turn your project into a jar package in idea
- The jar package download of Maven project appears (could not transfer artifact. Org mybatis:mybatis ）
- When Maven hits the jar package, an error is reported when executing install, and the symbol cannot be found in a line
- Mybatis idea environment integration jar package
- The introduction of third-party jar package in mavn project results in classnotfoundexception
- Research on Maven management of Java project pom.xml The jar package error is reported, but the project is running normally
- The remote port occupation of Linux startup jar package script reports an error
- Depending on the custom component jar package, unable to read meta data for class appears after startup
- Failed to get the resources path in the jar package, reporting an error null pointer
- Local can link to the server database, upload jar package to the server will report an error
- [solution] the resource file cannot be found in the jar package of Java
- [Solved] Scala signature package has wrong version expected: 5.0 found: 5.2 in package.class