The following method did not exist （maven依赖冲突解决全记录）

先贴报错：

***************************
APPLICATION FAILED TO START
***************************

Description:

An attempt was made to call a method that does not exist. The attempt was made from the following location:
 com.casic.cpdm.access.service.AdministrativeDomainServiceImpl.createAdministrativeDomain(AdministrativeDomainServiceImpl.java:194)

The following method did not exist:
   com.casic.cpdm.access.entity.AdministrativeDomain.setContextType(Lcom/casic/cpdm/access/dto/ContextTypeEnum;)V

The calling method's class, com.casic.cpdm.access.service.AdministrativeDomainServiceImpl, was loaded from the following location:

    jar:file:/opt/3y-cpdm/business-service.jar!/BOOT-INF/lib/cplm-cloud-foundation-service-2.1.0-SNAPSHOT.jar!/com/casic/cpdm/access/service/AdministrativeDomainServiceImpl.class

The called method's class, com.casic.cpdm.access.entity.AdministrativeDomain, is available from the following locations:

    jar:file:/opt/3y-cpdm/business-service.jar!/BOOT-INF/lib/cplm-cloud-admin-api-2.1.0-SNAPSHOT.jar!/com/casic/cpdm/access/entity/AdministrativeDomain.class
    jar:file:/opt/3y-cpdm/business-service.jar!/BOOT-INF/lib/cplm-cloud-foundation-api-2.1.0-SNAPSHOT.jar!/com/casic/cpdm/access/entity/AdministrativeDomain.class

The called method's class hierarchy was loaded from the following locations:

    com.casic.cpdm.access.entity.AdministrativeDomain: jar:file:/opt/3y-cpdm/business-service.jar!/BOOT-INF/lib/cplm-cloud-admin-api-2.1.0-SNAPSHOT.jar!/
    com.casic.cplm.data.AbstractEntity: jar:file:/opt/3y-cpdm/business-service.jar!/BOOT-INF/lib/cplm-cloud-starter-jpa-2.1.0-SNAPSHOT.jar!/
    com.casic.cplm.data.AbstractPersistable: jar:file:/opt/3y-cpdm/business-service.jar!/BOOT-INF/lib/cplm-cloud-starter-jpa-2.1.0-SNAPSHOT.jar!/

Action:

Correct the classpath of your application so that it contains compatible versions of the classes com.casic.cpdm.access.service.AdministrativeDomainServiceImpl and com.casic.cpdm.access.entity.AdministrativeDomain

以上可以看到是AdministrativeDomain.class在两处都有，引起冲突
解决办法是，干掉其中一个