The reason why Maven installs x is that Maven will generate a *. Lastupdated file for the jar file that can’t be downloaded. If it doesn’t kill the *. Lastupdated file, it won’t download the jar for you again. So, kill the *. Lastupdated guy and update it again
Original text: https://blog.csdn.net/qq_ 22843051/article/details/79765040
Read More:
- New Maven project– pom.xml report errors
- Maven project pom.xml The solution of error report in execution of
- Idea2020.2 encountered pom.xml The problem of file error report in Maven plug-in tomcat7
- About maven Pom.xml Personal solutions to reporting errors!!!
- Solution of maven pom.xml dependency invalidation in IntelliJ
- Import Maven project pom.xml File error
- Error in pom.xml file of sub module of Maven aggregation project
- Where’s Maven pom.xml Configure aliyun warehouse in
- Maven of springboot project pom.xml Unknown error in the first line of the file
- Maven project pom.xml Solutions to error reporting
- pom.xml Depending on the error report, the problem of missing artifact XXX is solved
- Application of IntelliJ idea in Maven project pom.xml Add dependency
- The spring boot project was first created, pom.xml The error is Maven configuration problem. How to solve it?
- Research on Maven management of Java project pom.xml The jar package error is reported, but the project is running normally
- Error in Maven POM file: multiple annotations found at this line solution
- Error in STS importing POM file of Maven project
- Error in pom.xml dependency version number in idea
- Android is Stuck in Download maven-metadata.xml [How to Solve]
- Error in the project tag in the POM file of Maven project: failure to transfer
- Error in Maven packaging web project: webxml attribute is required (or pre existing WEB-INF)/ web.xml if executing in update)