An attempt was made to call the method com.google.gson.GsonBuilder.setLenient()Lcom/google/gson/GsonBuilder; but it does not exist. Its class, com.google.gson.GsonBuilder, is available from the foll

 SLF4J: Class path contains multiple SLF4J bindings.
 SLF4J: Found binding in [jar:file:/G:/sharp/repo/ch/qos/logback/logback-classic/1.2.3/logback-classic-

 1.2.3.jar!/org/slf4j/impl/StaticLoggerBinder.class]
 SLF4J: Found binding in [jar:file:/G:/sharp/repo/org/slf4j/slf4j-log4j12/1.7.25/slf4j-log4j12-

 1.7.25.jar!/org/slf4j/impl/StaticLoggerBinder.class]
 SLF4J: See http://www.slf4j.org/codes.html#multiple_bindings for an explanation.
 SLF4J: Actual binding is of type [ch.qos.logback.classic.util.ContextSelectorStaticBinder]

   .   ____          _            __ _ _
  /\\ / ___'_ __ _ _(_)_ __  __ _ \ \ \ \
 ( ( )\___ | '_ | '_| | '_ \/ _` | \ \ \ \
  \\/  ___)| |_)| | | | | || (_| |  ) ) ) )
   '  |____| .__|_| |_|_| |_\__, | / / / /
  =========|_|==============|___/=/_/_/_/
  :: Spring Boot ::        (v2.1.0.RELEASE)

 2019-01-10 09:20:41.911 [main] INFO  com.sharp.forward.SharpServiceApplication - Starting SharpServiceApplication on 

 hh-PC with PID 7440 (G:\worksheet\sharp-service\target\classes started by Administrator in G:\worksheet\sharp-service)
 2019-01-10 09:20:41.913 [main] INFO  com.sharp.forward.SharpServiceApplication - The following profiles are active: 

 local
 log4j:WARN No appenders could be found for logger (com.alibaba.dubbo.common.logger.LoggerFactory).
 log4j:WARN Please initialize the log4j system properly.
 log4j:WARN See http://logging.apache.org/log4j/1.2/faq.html#noconfig for more info.
 2019-01-10 09:20:43.101 [main] INFO  org.springframework.data.repository.config.RepositoryConfigurationDelegate - 

 Bootstrapping Spring Data repositories in DEFAULT mode.
 2019-01-10 09:20:43.126 [main] INFO  org.springframework.data.repository.config.RepositoryConfigurationDelegate - 

 Finished Spring Data repository scanning in 15ms. Found 0 repository interfaces.
 2019-01-10 09:20:43.506 [main] INFO  org.springframework.context.support.PostProcessorRegistrationDelegate

 $BeanPostProcessorChecker - Bean 'org.springframework.transaction.annotation.ProxyTransactionManagementConfiguration' of 

 type [org.springframework.transaction.annotation.ProxyTransactionManagementConfiguration$$EnhancerBySpringCGLIB$

 $d77381ec] is not eligible for getting processed by all BeanPostProcessors (for example: not eligible for auto-proxying)
 2019-01-10 09:20:43.915 [main] INFO  org.springframework.boot.web.embedded.tomcat.TomcatWebServer - Tomcat initialized 

 with port(s): 8080 (http)
 2019-01-10 09:20:43.929 [main] INFO  org.apache.coyote.http11.Http11NioProtocol - Initializing ProtocolHandler ["http-

 nio-8080"]
 2019-01-10 09:20:43.935 [main] INFO  org.apache.catalina.core.StandardService - Starting service [Tomcat]
 2019-01-10 09:20:43.936 [main] INFO  org.apache.catalina.core.StandardEngine - Starting Servlet Engine: Apache 

 Tomcat/9.0.12
 2019-01-10 09:20:43.944 [main] INFO  org.apache.catalina.core.AprLifecycleListener - The APR based Apache Tomcat Native 

 library which allows optimal performance in production environments was not found on the java.library.path: [D:

 \xxxSoft\java\jre1.8\bin;C:\Windows\Sun\Java\bin;C:\Windows\system32;C:

 \Windows;D:/xxxSoft/java/jre1.8/bin/server;D:/xxxSoft/java/jre1.8/bin;D:/xxxSoft/java/jre1.8/lib/amd64;C:

 \Program Files (x86)\Common Files\Oracle\Java\javapath;C:\Windows\system32;C:\Windows;C:\Windows\System32\Wbem;C:

 \Windows\System32\WindowsPowerShell\v1.0\;C:\Program Files (x86)\Java\jre7;D:\xxxSoft\java\jdk1.8\bin;D:

 \xxxSoft\java\jdk1.8\jre\bin;D:\xxxSoft\git\Git\cmd;D:\xxxSoft\svn\bin;D:\xxxSoft\maven\apache-maven-

 3.3.9-bin\apache-maven-3.3.9\bin;C:\Program Files\bin;D:\xxxSoft\zookeeper/bin;D:\xxxSoft\zookeeper/conf;D:

 \project-x\;D:\xxxSoft\eclipse4.8\eclipse;;.]
 2019-01-10 09:20:44.063 [main] INFO  org.apache.catalina.core.ContainerBase.[Tomcat].[localhost].[/] - Initializing 

 Spring embedded WebApplicationContext
 2019-01-10 09:20:44.063 [main] INFO  org.springframework.web.context.ContextLoader - Root WebApplicationContext: 

 initialization completed in 2102 ms
 2019-01-10 09:20:44.091 [main] INFO  org.springframework.boot.web.servlet.ServletRegistrationBean - Servlet 

 dispatcherServlet mapped to [/]
 2019-01-10 09:20:44.095 [main] INFO  org.springframework.boot.web.servlet.FilterRegistrationBean - Mapping filter: 

 'characterEncodingFilter' to: [/*]
 2019-01-10 09:20:44.095 [main] INFO  org.springframework.boot.web.servlet.FilterRegistrationBean - Mapping filter: 

 'hiddenHttpMethodFilter' to: [/*]
 2019-01-10 09:20:44.095 [main] INFO  org.springframework.boot.web.servlet.FilterRegistrationBean - Mapping filter: 

 'formContentFilter' to: [/*]
 2019-01-10 09:20:44.095 [main] INFO  org.springframework.boot.web.servlet.FilterRegistrationBean - Mapping filter: 

 'requestContextFilter' to: [/*]
 2019-01-10 09:20:44.222 [main] INFO  com.zaxxer.hikari.HikariDataSource - HikariPool-1 - Starting...
 Thu Jan 10 09:20:44 CST 2019 WARN: Establishing SSL connection without server's identity verification is not 

 recommended. According to MySQL 5.5.45+, 5.6.26+ and 5.7.6+ requirements SSL connection must be established by default 

 if explicit option isn't set. For compliance with existing applications not using SSL the verifyServerCertificate 

 property is set to 'false'. You need either to explicitly disable SSL by setting useSSL=false, or set useSSL=true and 

 provide truststore for server certificate verification.
 2019-01-10 09:20:44.653 [main] INFO  com.zaxxer.hikari.HikariDataSource - HikariPool-1 - Start completed.
 2019-01-10 09:20:44.708 [main] INFO  org.hibernate.jpa.internal.util.LogHelper - HHH000204: Processing 

 PersistenceUnitInfo [
     name: default
     ...]
 Thu Jan 10 09:20:44 CST 2019 WARN: Establishing SSL connection without server's identity verification is not 

 recommended. According to MySQL 5.5.45+, 5.6.26+ and 5.7.6+ requirements SSL connection must be established by default 

 if explicit option isn't set. For compliance with existing applications not using SSL the verifyServerCertificate 

 property is set to 'false'. You need either to explicitly disable SSL by setting useSSL=false, or set useSSL=true and 

 provide truststore for server certificate verification.
 Thu Jan 10 09:20:44 CST 2019 WARN: Establishing SSL connection without server's identity verification is not 

 recommended. According to MySQL 5.5.45+, 5.6.26+ and 5.7.6+ requirements SSL connection must be established by default 

 if explicit option isn't set. For compliance with existing applications not using SSL the verifyServerCertificate 

 property is set to 'false'. You need either to explicitly disable SSL by setting useSSL=false, or set useSSL=true and 

 provide truststore for server certificate verification.
 2019-01-10 09:20:44.805 [main] INFO  org.hibernate.Version - HHH000412: Hibernate Core {5.3.7.Final}
 2019-01-10 09:20:44.806 [main] INFO  org.hibernate.cfg.Environment - HHH000206: hibernate.properties not found
 Thu Jan 10 09:20:44 CST 2019 WARN: Establishing SSL connection without server's identity verification is not 

 recommended. According to MySQL 5.5.45+, 5.6.26+ and 5.7.6+ requirements SSL connection must be established by default 

 if explicit option isn't set. For compliance with existing applications not using SSL the verifyServerCertificate 

 property is set to 'false'. You need either to explicitly disable SSL by setting useSSL=false, or set useSSL=true and 

 provide truststore for server certificate verification.
 Thu Jan 10 09:20:44 CST 2019 WARN: Establishing SSL connection without server's identity verification is not 

 recommended. According to MySQL 5.5.45+, 5.6.26+ and 5.7.6+ requirements SSL connection must be established by default 

 if explicit option isn't set. For compliance with existing applications not using SSL the verifyServerCertificate 

 property is set to 'false'. You need either to explicitly disable SSL by setting useSSL=false, or set useSSL=true and 

 provide truststore for server certificate verification.
 Thu Jan 10 09:20:44 CST 2019 WARN: Establishing SSL connection without server's identity verification is not 

 recommended. According to MySQL 5.5.45+, 5.6.26+ and 5.7.6+ requirements SSL connection must be established by default 

 if explicit option isn't set. For compliance with existing applications not using SSL the verifyServerCertificate 

 property is set to 'false'. You need either to explicitly disable SSL by setting useSSL=false, or set useSSL=true and 

 provide truststore for server certificate verification.
 Thu Jan 10 09:20:44 CST 2019 WARN: Establishing SSL connection without server's identity verification is not 

 recommended. According to MySQL 5.5.45+, 5.6.26+ and 5.7.6+ requirements SSL connection must be established by default 

 if explicit option isn't set. For compliance with existing applications not using SSL the verifyServerCertificate 

 property is set to 'false'. You need either to explicitly disable SSL by setting useSSL=false, or set useSSL=true and 

 provide truststore for server certificate verification.
 Thu Jan 10 09:20:44 CST 2019 WARN: Establishing SSL connection without server's identity verification is not 

 recommended. According to MySQL 5.5.45+, 5.6.26+ and 5.7.6+ requirements SSL connection must be established by default 

 if explicit option isn't set. For compliance with existing applications not using SSL the verifyServerCertificate 

 property is set to 'false'. You need either to explicitly disable SSL by setting useSSL=false, or set useSSL=true and 

 provide truststore for server certificate verification.
 Thu Jan 10 09:20:44 CST 2019 WARN: Establishing SSL connection without server's identity verification is not 

 recommended. According to MySQL 5.5.45+, 5.6.26+ and 5.7.6+ requirements SSL connection must be established by default 

 if explicit option isn't set. For compliance with existing applications not using SSL the verifyServerCertificate 

 property is set to 'false'. You need either to explicitly disable SSL by setting useSSL=false, or set useSSL=true and 

 provide truststore for server certificate verification.
 Thu Jan 10 09:20:44 CST 2019 WARN: Establishing SSL connection without server's identity verification is not 

 recommended. According to MySQL 5.5.45+, 5.6.26+ and 5.7.6+ requirements SSL connection must be established by default 

 if explicit option isn't set. For compliance with existing applications not using SSL the verifyServerCertificate 

 property is set to 'false'. You need either to explicitly disable SSL by setting useSSL=false, or set useSSL=true and 

 provide truststore for server certificate verification.
 2019-01-10 09:20:44.986 [main] INFO  org.hibernate.annotations.common.Version - HCANN000001: Hibernate Commons 

 Annotations {5.0.4.Final}
 2019-01-10 09:20:45.140 [main] INFO  org.hibernate.dialect.Dialect - HHH000400: Using dialect: 

 org.hibernate.dialect.MySQL5Dialect
 2019-01-10 09:20:45.365 [main] INFO  org.springframework.orm.jpa.LocalContainerEntityManagerFactoryBean - Initialized 

 JPA EntityManagerFactory for persistence unit 'default'
 2019-01-10 09:20:45.888 [main] INFO  org.springframework.scheduling.concurrent.ThreadPoolTaskExecutor - Initializing 

 ExecutorService 'applicationTaskExecutor'
 2019-01-10 09:20:45.929 [main] WARN  org.springframework.boot.autoconfigure.orm.jpa.JpaBaseConfiguration

 $JpaWebConfiguration$JpaWebMvcConfiguration - spring.jpa.open-in-view is enabled by default. Therefore, database queries 

 may be performed during view rendering. Explicitly configure spring.jpa.open-in-view to disable this warning
 2019-01-10 09:20:46.057 [main] WARN  

 org.springframework.boot.web.servlet.context.AnnotationConfigServletWebServerApplicationContext - Exception encountered 

 during context initialization - cancelling refresh attempt: org.springframework.beans.factory.BeanCreationException: 

 Error creating bean with name 'gsonBuilder' defined in class path resource 

 [org/springframework/boot/autoconfigure/gson/GsonAutoConfiguration.class]: Bean instantiation via factory method failed; 

 nested exception is org.springframework.beans.BeanInstantiationException: Failed to instantiate 

 [com.google.gson.GsonBuilder]: Factory method 'gsonBuilder' threw exception; nested exception is 

 java.lang.BootstrapMethodError: java.lang.NoSuchMethodError: com.google.gson.GsonBuilder.setLenient()

 Lcom/google/gson/GsonBuilder;
 2019-01-10 09:20:46.057 [main] INFO  org.springframework.scheduling.concurrent.ThreadPoolTaskExecutor - Shutting down 

 ExecutorService 'applicationTaskExecutor'
 2019-01-10 09:20:46.058 [main] INFO  org.springframework.orm.jpa.LocalContainerEntityManagerFactoryBean - Closing JPA 

 EntityManagerFactory for persistence unit 'default'
 2019-01-10 09:20:46.061 [main] INFO  com.zaxxer.hikari.HikariDataSource - HikariPool-1 - Shutdown initiated...
 2019-01-10 09:20:46.068 [main] INFO  com.zaxxer.hikari.HikariDataSource - HikariPool-1 - Shutdown completed.
 2019-01-10 09:20:46.070 [main] INFO  org.apache.catalina.core.StandardService - Stopping service [Tomcat]
 2019-01-10 09:20:46.083 [main] INFO  

 org.springframework.boot.autoconfigure.logging.ConditionEvaluationReportLoggingListener - 

 Error starting ApplicationContext. To display the conditions report re-run your application with 'debug' enabled.
 2019-01-10 09:20:46.085 [main] ERROR org.springframework.boot.diagnostics.LoggingFailureAnalysisReporter - 

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

 Description:

 An attempt was made to call the method com.google.gson.GsonBuilder.setLenient()Lcom/google/gson/GsonBuilder; but it does 

 not exist. Its class, com.google.gson.GsonBuilder, is available from the following locations:

     jar:file:/G:/lib/gson-2.3.1.jar!/com/google/gson/GsonBuilder.class

 It was loaded from the following location:

     file:/G:/lib/gson-2.3.1.jar

 Action:

 Correct the classpath of your application so that it contains a single, compatible version of 

 com.google.gson.GsonBuilder

提升了版本2.7，2.8.2，但是均没有解决版本冲突的问题，最后发现，是我之前手动添加过gson.jar。删除即可。比较常规，但是由于用maven管理jar包，在pom.xml中找不到冲突的jar所以在这里记录一下，提个醒。下面是先删除本地jar之后的现象，再删除这些就可以了