Scenario: The project relies on spring 4.3.0 and spring 5.2.5, and there is a conflict, so the dependency on 5.2.5 is deleted
Action: Delete the dependency of 5.2.5 under dependency in the pom.xml file
After deleting, I found that the jar package still exists in the dependencies of the project. The exception still exists.
Solution: After refreshing the maven dependencies, it was found that the modified pom file took effect
Extension: modify the version number of dependencies, and add dependencies also need to be refreshed according to this method