Preface:
1，找不到文件 The container 'Maven Dependencies' references non existing library '${groupid}/${artifactid}-${version}.jar'
2, first introduced maven dependent projects, pom.xml file error
3，报错，Project build error: Non-resolvable parent POM
text:
1，找不到文件 The container 'Maven Dependencies' references non existing library '${groupid}/${artifactid}-${version}.jar'
Reason: Failed to download file, generate * .lastUpdated file. Cause the file is not downloaded over, I will not go again pulled
Solution: Find * .lastUpdated, and then delete all the files found. Re Maven Update Project
Reference blog:
Maven Dependency download failures - duangr personal page - OSCHINA
https://my.oschina.net/duangr/blog/182134
Maven appear at the end .lastUpdated document problems and solutions - software development other - a red-black coalition
https://www.2cto.com/kf/201802/718147.html
2, first introduced maven dependent projects, pom.xml file error
The first will be a lot depends on the introduction of errors
Solution: Open the project in the wrong directory cmd, enter the command line mvn compile, after a successful run, back IDE (eclipse or IDEA), re Maven Update Project
Reference blog:
Spring Tool Suite for the first time pom.xml dependent errors appear Solution - just memory - ITeye blog
https://fair-jm.iteye.com/blog/1995098
3，报错，Project build error: Non-resolvable parent POM
Cause: The version information is inconsistent parent modules and sub-modules introduced
Reference blog:
How myeclipse guide maven project to load the missing JAR error "Project build error: Non-resolvable parent POM" -CSDN Forum
https://bbs.csdn.net/topics/391044398