Maven project pom.xml Solutions to error reporting

1. Error in pom.xml
Similar: Missing an artifact org. Springframework: spring – JDBC: jar: 3.2.4. RELEASE such errors, suggest a jar package.
I’ve run into this problem several times before. Every time I solve it, I forget it the next time. Make a note of it.
Force Update of Snapshots/Releases: Force Update of Snapshots/Releases: Force Update of Snapshots/Releases: Force Update of Snapshots/Releases: Force Update of Snapshots/Releases
SpringBoot error -Due to missing ServletWebServerFactory
Update 2019.6.24

2019-06-24 14:09:15.039  INFO 17356 --- [           main] trationDelegate$BeanPostProcessorChecker : Bean 'org.springframework.amqp.rabbit.annotation.RabbitBootstrapConfiguration' of type [org.springframework.amqp.rabbit.annotation.RabbitBootstrapConfiguration$$EnhancerBySpringCGLIB$$6d407ba3] is not eligible for getting processed by all BeanPostProcessors (for example: not eligible for auto-proxying)
2019-06-24 14:09:15.592  WARN 17356 --- [           main] ConfigServletWebServerApplicationContext : Exception encountered during context initialization - cancelling refresh attempt: org.springframework.context.ApplicationContextException: Unable to start web server; nested exception is org.springframework.context.ApplicationContextException: Unable to start ServletWebServerApplicationContext due to missing ServletWebServerFactory bean.

ServletWebServerFactoryass references o>pache.catalina package>e,
It then looks at the JAR package that has been introduced and finds that there is no such package.
To solve this problem, add the following dependencies:


tomcat-embedbed embed embed embed embedtomcat-embed embed embed embed embed embed embed I did not introduce the spring-boot-starter-webpendency, which resulted in the incorrect introduction of Tomcat related packages, rather than a dependency conflict or other issue.
3, to be continued…
If you run into problems with Maven errors in the future, you will remember them here.

Read More: