使用maven管理依赖，spring版本冲突解决 java.lang.NoSuchMethodError: org.springframework.core.GenericTypeResolver.r

最新推荐文章于 2024-02-16 17:33:56 发布

原创最新推荐文章于 2024-02-16 17:33:56 发布 · 1.9w 阅读

1 ·

CC 4.0 BY-SA版权

文章标签：

#spring #maven #cobarclient

spring 同时被 2 个专栏收录

18 篇文章

订阅专栏

maven

12 篇文章

订阅专栏

在使用Maven管理依赖时遇到由于spring2.5和3.1版本冲突导致的`java.lang.NoSuchMethodError`。解决方案是在含有spring2.5的依赖中添加exclusion，确保统一使用相同版本的Spring库。

摘要生成于 C知道，由 DeepSeek-R1 满血版支持，前往体验 >

报错异常堆栈：

java.lang.NoSuchMethodError: org.springframework.core.GenericTypeResolver.resolveTypeArguments(Ljava/lang/Class;Ljava/lang/Class;)[Ljava/lang/Class;
	at org.springframework.core.convert.support.GenericConversionService.getRequiredTypeInfo(GenericConversionService.java:275)
	at org.springframework.core.convert.support.GenericConversionService.addConverter(GenericConversionService.java:93)
	at org.springframework.core.convert.support.DefaultConversionService.addScalarConverters(DefaultConversionService.java:61)
	at org.springframework.core.convert.support.DefaultConversionService.addDefaultConverters(DefaultConversionService.java:53)
	at org.springframework.core.convert.support.DefaultConversionService.<init>(DefaultConversionService.java:42)
	at org.springframework.core.env.AbstractPropertyResolver.<init>(AbstractPropertyResolver.java:44)
	at org.springframework.core.env.PropertySourcesPropertyResolver.<init>(PropertySourcesPropertyResolver.java:42)
	at org.springframework.core.env.AbstractEnvironment.<init>(AbstractEnvironment.java:101)
	at org.springframework.core.env.StandardEnvironment.<init>(StandardEnvironment.java:54)
	at org.springframework.web.context.support.StandardServletEnvironment.<init>(StandardServletEnvironment.java:43)
	at org.springframework.web.servlet.HttpServletBean.<init>(HttpServletBean.java:90)
	at org.springframework.web.servlet.FrameworkServlet.<init>(FrameworkServlet.java:211)
	at org.springframework.web.servlet.DispatcherServlet.<init>(DispatcherServlet.java:323)
	at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
	at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:39)
	at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:27)
	at java.lang.reflect.Constructor.newInstance(Constructor.java:513)
	at java.lang.Class.newInstance0(Class.java:357)
	at java.lang.Class.newInstance(Class.java:310)
	at org.apache.catalina.core.DefaultInstanceManager.newInstance(DefaultInstanceManager.java:140)
	at org.apache.catalina.core.StandardWrapper.loadServlet(StandardWrapper.java:1148)
	at org.apache.catalina.core.StandardWrapper.load(StandardWrapper.java:1087)
	at org.apache.catalina.core.StandardContext.loadOnStartup(StandardContext.java:5210)
	at org.apache.catalina.core.StandardContext.startInternal(StandardContext.java:5493)
	at org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:150)
	at org.apache.catalina.core.ContainerBase$StartChild.call(ContainerBase.java:1559)
	at org.apache.catalina.core.ContainerBase$StartChild.call(ContainerBase.java:1549)
	at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303)
	at java.util.concurrent.FutureTask.run(FutureTask.java:138)
	at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:895)
	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:918)
	at java.lang.Thread.run(Thread.java:695)

原因是maven的dependency中，依赖了不同版本的spring，spring2.5和3.1的冲突导致的。

解决办法是将使用了srping2.5的dependency加上exclusion，例如：

    <dependency>

   	<groupId>com.alibaba.cobar</groupId>
    	<artifactId>cobar-client</artifactId>
    	<version>1.0.5</version>
        <exclusions>
		    <exclusion>
		       <groupId>org.springframework</groupId>
		       <artifactId>spring</artifactId>
		    </exclusion>
		 </exclusions>	
    </dependency>