this is obviously caused by version conflicts.
you can try to solve this problem:

1. find the jar where the exception class exists
2. View the dependencies in the project, mvn dependency:tree
3. find dependencies and dependent versions from dependency:tree
4. manually upgrade or downgrade conflict jar (this requires repeated attempts)

but if you are using spring-boot, and the third-party framework has been integrated by spring-boot, you can try to remove the custom version and use the version defined in spring-boot-parent