spring gradle 更新依赖导致的依赖冲突

最新推荐文章于 2024-01-13 09:47:26 发布
最新推荐文章于 2024-01-13 09:47:26 发布
阅读量1.1k 收藏
点赞数
分类专栏： SpringBoot 文章标签： java spring gradle
版权声明：本文为博主原创文章，遵循 CC 4.0 BY-SA 版权协议，转载请附上原文出处链接和本声明。
本文链接：https://blog.csdn.net/leean950806/article/details/78136745
版权

问题：

在项目中更新了一个依赖包的版本，之后项目测试报错，有bean无法装配，百思不得其解。经师兄指点发现是依赖冲突。报错如下：

Sep 28, 2017 7:00:12 PM org.springframework.test.context.TestContextManager prepareTestInstance
SEVERE: Caught exception while allowing TestExecutionListener [org.springframework.test.context.support.DependencyInjectionTestExecutionListener@64f6106c] to prepare test instance [省略项目名称@20a116a0]
java.lang.IllegalStateException: Failed to load ApplicationContext
	at org.springframework.test.context.cache.DefaultCacheAwareContextLoaderDelegate.loadContext(DefaultCacheAwareContextLoaderDelegate.java:124)
	at org.springframework.test.context.support.DefaultTestContext.getApplicationContext(DefaultTestContext.java:83)
	at org.springframework.test.context.support.DependencyInjectionTestExecutionListener.injectDependencies(DependencyInjectionTestExecutionListener.java:117)
	at org.springframework.test.context.support.DependencyInjectionTestExecutionListener.prepareTestInstance(DependencyInjectionTestExecutionListener.java:83)
	at org.springframework.test.context.TestContextManager.prepareTestInstance(TestContextManager.java:228)
	at org.springframework.test.context.junit4.SpringJUnit4ClassRunner.createTest(SpringJUnit4ClassRunner.java:230)
	at org.springframework.test.context.junit4.SpringJUnit4ClassRunner$1.runReflectiveCall(SpringJUnit4ClassRunner.java:289)
	at org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:12)
	at org.springframework.test.context.junit4.SpringJUnit4ClassRunner.methodBlock(SpringJUnit4ClassRunner.java:291)
	at org.springframework.test.context.junit4.SpringJUnit4ClassRunner.runChild(SpringJUnit4ClassRunner.java:249)
	at org.springframework.test.context.junit4.SpringJUnit4ClassRunner.runChild(SpringJUnit4ClassRunner.java:89)
	at org.junit.runners.ParentRunner$3.run(ParentRunner.java:290)
	at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:71)
	at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:288)
	at org.junit.runners.ParentRunner.access$000(ParentRunner.java:58)
	at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:268)
	at org.springframework.test.context.junit4.statements.RunBeforeTestClassCallbacks.evaluate(RunBeforeTestClassCallbacks.java:61)
	at org.springframework.test.context.junit4.statements.RunAfterTestClassCallbacks.evaluate(RunAfterTestClassCallbacks.java:70)
	at org.junit.runners.ParentRunner.run(ParentRunner.java:363)
	at org.springframework.test.context.junit4.SpringJUnit4ClassRunner.run(SpringJUnit4ClassRunner.java:193)
	at org.junit.runner.JUnitCore.run(JUnitCore.java:137)
	at com.intellij.junit4.JUnit4IdeaTestRunner.startRunnerWithArgs(JUnit4IdeaTestRunner.java:68)
	at com.intellij.rt.execution.junit.IdeaTestRunner$Repeater.startRunnerWithArgs(IdeaTestRunner.java:47)
	at com.intellij.rt.execution.junit.JUnitStarter.prepareStreamsAndStart(JUnitStarter.java:242)
	at com.intellij.rt.execution.junit.JUnitStarter.main(JUnitStarter.java:70)
Caused by: org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'infoEndpoint' defined in class path resource [org/springframework/boot/actuate/autoconfigure/EndpointAutoConfiguration.class]: Bean instantiation via factory method failed; nested exception is org.springframework.beans.BeanInstantiationException: Failed to instantiate [org.springframework.boot.actuate.endpoint.InfoEndpoint]: Factory method 'infoEndpoint' threw exception; nested exception is java.lang.NoSuchMethodError: org.springframework.boot.bind.PropertiesConfigurationFactory.setProperties(Ljava/util/Properties;)V
	at org.springframework.beans.factory.support.ConstructorResolver.instantiateUsingFactoryMethod(ConstructorResolver.java:599)
	at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.instantiateUsingFactoryMethod(AbstractAutowireCapableBeanFactory.java:1173)
	at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.createBeanInstance(AbstractAutowireCapableBeanFactory.java:1067)
	at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.doCreateBean(AbstractAutowireCapableBeanFactory.java:513)
	at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.createBean(AbstractAutowireCapableBeanFactory.java:483)
	at org.springframework.beans.factory.support.AbstractBeanFactory$1.getObject(AbstractBeanFactory.java:306)
	at org.springframework.beans.factory.support.DefaultSingletonBeanRegistry.getSingleton(DefaultSingletonBeanRegistry.java:230)
	at org.springframework.beans.factory.support.AbstractBeanFactory.doGetBean(AbstractBeanFactory.java:302)
	at org.springframework.beans.factory.support.AbstractBeanFactory.getBean(AbstractBeanFactory.java:197)
	at org.springframework.beans.factory.support.DefaultListableBeanFactory.preInstantiateSingletons(DefaultListableBeanFactory.java:761)
	at org.springframework.context.support.AbstractApplicationContext.finishBeanFactoryInitialization(AbstractApplicationContext.java:867)
	at org.springframework.context.support.AbstractApplicationContext.refresh(AbstractApplicationContext.java:543)
	at org.springframework.test.context.support.AbstractGenericContextLoader.loadContext(AbstractGenericContextLoader.java:125)
	at org.springframework.test.context.support.AbstractGenericContextLoader.loadContext(AbstractGenericContextLoader.java:60)
	at org.springframework.test.context.support.AbstractDelegatingSmartContextLoader.delegateLoading(AbstractDelegatingSmartContextLoader.java:109)
	at org.springframework.test.context.support.AbstractDelegatingSmartContextLoader.loadContext(AbstractDelegatingSmartContextLoader.java:261)
	at org.springframework.test.context.cache.DefaultCacheAwareContextLoaderDelegate.loadContextInternal(DefaultCacheAwareContextLoaderDelegate.java:98)
	at org.springframework.test.context.cache.DefaultCacheAwareContextLoaderDelegate.loadContext(DefaultCacheAwareContextLoaderDelegate.java:116)
	... 24 more
Caused by: org.springframework.beans.BeanInstantiationException: Failed to instantiate [org.springframework.boot.actuate.endpoint.InfoEndpoint]: Factory method 'infoEndpoint' threw exception; nested exception is java.lang.NoSuchMethodError: org.springframework.boot.bind.PropertiesConfigurationFactory.setProperties(Ljava/util/Properties;)V
	at org.springframework.beans.factory.support.SimpleInstantiationStrategy.instantiate(SimpleInstantiationStrategy.java:189)
	at org.springframework.beans.factory.support.ConstructorResolver.instantiateUsingFactoryMethod(ConstructorResolver.java:588)
	... 41 more
Caused by: java.lang.NoSuchMethodError: org.springframework.boot.bind.PropertiesConfigurationFactory.setProperties(Ljava/util/Properties;)V
	at org.springframework.boot.actuate.autoconfigure.EndpointAutoConfiguration$InfoPropertiesConfiguration.gitInfo(EndpointAutoConfiguration.java:233)
	at org.springframework.boot.actuate.autoconfigure.EndpointAutoConfiguration.infoEndpoint(EndpointAutoConfiguration.java:128)
	at org.springframework.boot.actuate.autoconfigure.EndpointAutoConfiguration$$EnhancerBySpringCGLIB$$65554127.CGLIB$infoEndpoint$3(<generated>)
	at org.springframework.boot.actuate.autoconfigure.EndpointAutoConfiguration$$EnhancerBySpringCGLIB$$65554127$$FastClassBySpringCGLIB$$a6d263d3.invoke(<generated>)
	at org.springframework.cglib.proxy.MethodProxy.invokeSuper(MethodProxy.java:228)
	at org.springframework.context.annotation.ConfigurationClassEnhancer$BeanMethodInterceptor.intercept(ConfigurationClassEnhancer.java:358)
	at org.springframework.boot.actuate.autoconfigure.EndpointAutoConfiguration$$EnhancerBySpringCGLIB$$65554127.infoEndpoint(<generated>)
	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
	at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
	at java.lang.reflect.Method.invoke(Method.java:498)
	at org.springframework.beans.factory.support.SimpleInstantiationStrategy.instantiate(SimpleInstantiationStrategy.java:162)
	... 42 more


java.lang.IllegalStateException: Failed to load ApplicationContext

	at org.springframework.test.context.cache.DefaultCacheAwareContextLoaderDelegate.loadContext(DefaultCacheAwareContextLoaderDelegate.java:124)
	at org.springframework.test.context.support.DefaultTestContext.getApplicationContext(DefaultTestContext.java:83)
	at org.springframework.test.context.support.DependencyInjectionTestExecutionListener.injectDependencies(DependencyInjectionTestExecutionListener.java:117)
	at org.springframework.test.context.support.DependencyInjectionTestExecutionListener.prepareTestInstance(DependencyInjectionTestExecutionListener.java:83)
	at org.springframework.test.context.TestContextManager.prepareTestInstance(TestContextManager.java:228)
	at org.springframework.test.context.junit4.SpringJUnit4ClassRunner.createTest(SpringJUnit4ClassRunner.java:230)
	at org.springframework.test.context.junit4.SpringJUnit4ClassRunner$1.runReflectiveCall(SpringJUnit4ClassRunner.java:289)
	at org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:12)
	at org.springframework.test.context.junit4.SpringJUnit4ClassRunner.methodBlock(SpringJUnit4ClassRunner.java:291)
	at org.springframework.test.context.junit4.SpringJUnit4ClassRunner.runChild(SpringJUnit4ClassRunner.java:249)
	at org.springframework.test.context.junit4.SpringJUnit4ClassRunner.runChild(SpringJUnit4ClassRunner.java:89)
	at org.junit.runners.ParentRunner$3.run(ParentRunner.java:290)
	at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:71)
	at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:288)
	at org.junit.runners.ParentRunner.access$000(ParentRunner.java:58)
	at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:268)
	at org.springframework.test.context.junit4.statements.RunBeforeTestClassCallbacks.evaluate(RunBeforeTestClassCallbacks.java:61)
	at org.springframework.test.context.junit4.statements.RunAfterTestClassCallbacks.evaluate(RunAfterTestClassCallbacks.java:70)
	at org.junit.runners.ParentRunner.run(ParentRunner.java:363)
	at org.springframework.test.context.junit4.SpringJUnit4ClassRunner.run(SpringJUnit4ClassRunner.java:193)
	at org.junit.runner.JUnitCore.run(JUnitCore.java:137)
	at com.intellij.junit4.JUnit4IdeaTestRunner.startRunnerWithArgs(JUnit4IdeaTestRunner.java:68)
	at com.intellij.rt.execution.junit.IdeaTestRunner$Repeater.startRunnerWithArgs(IdeaTestRunner.java:47)
	at com.intellij.rt.execution.junit.JUnitStarter.prepareStreamsAndStart(JUnitStarter.java:242)
	at com.intellij.rt.execution.junit.JUnitStarter.main(JUnitStarter.java:70)
Caused by: org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'infoEndpoint' defined in class path resource [org/springframework/boot/actuate/autoconfigure/EndpointAutoConfiguration.class]: Bean instantiation via factory method failed; nested exception is org.springframework.beans.BeanInstantiationException: Failed to instantiate [org.springframework.boot.actuate.endpoint.InfoEndpoint]: Factory method 'infoEndpoint' threw exception; nested exception is java.lang.NoSuchMethodError: org.springframework.boot.bind.PropertiesConfigurationFactory.setProperties(Ljava/util/Properties;)V
	at org.springframework.beans.factory.support.ConstructorResolver.instantiateUsingFactoryMethod(ConstructorResolver.java:599)
	at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.instantiateUsingFactoryMethod(AbstractAutowireCapableBeanFactory.java:1173)
	at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.createBeanInstance(AbstractAutowireCapableBeanFactory.java:1067)
	at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.doCreateBean(AbstractAutowireCapableBeanFactory.java:513)
	at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.createBean(AbstractAutowireCapableBeanFactory.java:483)
	at org.springframework.beans.factory.support.AbstractBeanFactory$1.getObject(AbstractBeanFactory.java:306)
	at org.springframework.beans.factory.support.DefaultSingletonBeanRegistry.getSingleton(DefaultSingletonBeanRegistry.java:230)
	at org.springframework.beans.factory.support.AbstractBeanFactory.doGetBean(AbstractBeanFactory.java:302)
	at org.springframework.beans.factory.support.AbstractBeanFactory.getBean(AbstractBeanFactory.java:197)
	at org.springframework.beans.factory.support.DefaultListableBeanFactory.preInstantiateSingletons(DefaultListableBeanFactory.java:761)
	at org.springframework.context.support.AbstractApplicationContext.finishBeanFactoryInitialization(AbstractApplicationContext.java:867)
	at org.springframework.context.support.AbstractApplicationContext.refresh(AbstractApplicationContext.java:543)
	at org.springframework.test.context.support.AbstractGenericContextLoader.loadContext(AbstractGenericContextLoader.java:125)
	at org.springframework.test.context.support.AbstractGenericContextLoader.loadContext(AbstractGenericContextLoader.java:60)
	at org.springframework.test.context.support.AbstractDelegatingSmartContextLoader.delegateLoading(AbstractDelegatingSmartContextLoader.java:109)
	at org.springframework.test.context.support.AbstractDelegatingSmartContextLoader.loadContext(AbstractDelegatingSmartContextLoader.java:261)
	at org.springframework.test.context.cache.DefaultCacheAwareContextLoaderDelegate.loadContextInternal(DefaultCacheAwareContextLoaderDelegate.java:98)
	at org.springframework.test.context.cache.DefaultCacheAwareContextLoaderDelegate.loadContext(DefaultCacheAwareContextLoaderDelegate.java:116)
	... 24 more
Caused by: org.springframework.beans.BeanInstantiationException: Failed to instantiate [org.springframework.boot.actuate.endpoint.InfoEndpoint]: Factory method 'infoEndpoint' threw exception; nested exception is java.lang.NoSuchMethodError: org.springframework.boot.bind.PropertiesConfigurationFactory.setProperties(Ljava/util/Properties;)V
	at org.springframework.beans.factory.support.SimpleInstantiationStrategy.instantiate(SimpleInstantiationStrategy.java:189)
	at org.springframework.beans.factory.support.ConstructorResolver.instantiateUsingFactoryMethod(ConstructorResolver.java:588)
	... 41 more
Caused by: java.lang.NoSuchMethodError: org.springframework.boot.bind.PropertiesConfigurationFactory.setProperties(Ljava/util/Properties;)V
	at org.springframework.boot.actuate.autoconfigure.EndpointAutoConfiguration$InfoPropertiesConfiguration.gitInfo(EndpointAutoConfiguration.java:233)
	at org.springframework.boot.actuate.autoconfigure.EndpointAutoConfiguration.infoEndpoint(EndpointAutoConfiguration.java:128)
	at org.springframework.boot.actuate.autoconfigure.EndpointAutoConfiguration$$EnhancerBySpringCGLIB$$65554127.CGLIB$infoEndpoint$3(<generated>)
	at org.springframework.boot.actuate.autoconfigure.EndpointAutoConfiguration$$EnhancerBySpringCGLIB$$65554127$$FastClassBySpringCGLIB$$a6d263d3.invoke(<generated>)
	at org.springframework.cglib.proxy.MethodProxy.invokeSuper(MethodProxy.java:228)
	at org.springframework.context.annotation.ConfigurationClassEnhancer$BeanMethodInterceptor.intercept(ConfigurationClassEnhancer.java:358)
	at org.springframework.boot.actuate.autoconfigure.EndpointAutoConfiguration$$EnhancerBySpringCGLIB$$65554127.infoEndpoint(<generated>)
	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
	at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
	at java.lang.reflect.Method.invoke(Method.java:498)
	at org.springframework.beans.factory.support.SimpleInstantiationStrategy.instantiate(SimpleInstantiationStrategy.java:162)
	... 42 more

解决方法：

排除新加入的冲突的依赖项

compile ("省略冲突的依赖包") {
            exclude group: "org.springframework.boot" //冲突的依赖
            exclude group: "com.dianping.lion"
}

原因：

gradle对于项目的某个依赖包，为了保证同一个项目中的版本一致，会将依赖中版本最高的版本覆盖其他低的版本。

比如编译lion时，可能因为引用的项目的依赖中有更高版本的lion，而将项目直接依赖的lion更换成版本更高的包： com.dianping.lion:lion-client:2.0.8 -> 2.1.4

一些高版本的依赖包没有向下兼容，缺少了一部分的类或者功能，导致了测试时报bean装配错误


因为在这个项目中，报冲突的依赖包是作为RPC接口引入的，可以直接排除冲突的依赖项不用担心影响引入接口的功能。如果引入需要调用实际功能的依赖，可能就要调整项目代码来做兼容了

尤里安龙卷风
关注
  • 0
    点赞
  • 踩
  • 0
    收藏
    觉得还不错? 一键收藏
  • 0
    评论
专栏目录
SpringBoot单元测试问题
kongkongyanan的博客
01-15 1422
 哈喽大家好，今天跟大家分享下在项目中报错，查错时遇见的坑，SpringBoot单元测试时报以下错误 java.lang.IllegalStateException: Failed to load ApplicationContext at org.springframework.test.context.cache.DefaultCacheAwareContextLoaderDelegat...
Gradle-spring依赖包依赖包
10-31
了解这些文件的用途有助于我们更好地管理和优化Gradle构建过程，尤其是在解决依赖冲突、调试问题或提升构建效率时。 总的来说，"Gradle-spring依赖包依赖包"涉及到的关键点在于如何使用Gradle管理Spring框架的依赖...
Intellij 运行gradle单元测试失败
baidu_27842749的博客
12-08 920
Intellij 运行gradle单元测试失败，情况一 Failed to load ApplicationContext java.lang.IllegalStateException: Failed to load ApplicationContext at org.springframework.test.context.cache.DefaultCacheAwareContextLoaderDelegate.loadContext(DefaultCacheAwareContextLoad...
SpringTest的时候报错
weixin_42594143的博客
09-20 938
SpringTest的时候报错: 警告: Exception encountered during context initialization - cancelling refresh attempt: org.springframework.beans.factory.BeanCreationException: Error creating bean with name ‘sqlSessionFactory’ defined in class path resource [applicationCon
Gradle升级篇
qq_38386085的博客
09-27 2840
1.构建脚本： Gradle构建中的两个基本概念是项目（project）和任务（task），每个构建至少包含一个项目，项目中包含一个或多个任务。在多项目构建中，一个项目可以依赖于其他项目；类似的，任务可以形成一个依赖关系图来确保他们的执行顺序。 1.1项目（project）： 一个项目代表一个正在构建的组件（比如一个jar文件），当构建启动后，Gradle会基于build.gradle实例化...
idea gradle项目神神叨叨莫名报错的解决
weixin_43090275的博客
05-11 305
以下解决方法不一定次次有用 偶尔有用的我就写在这里了 1.重新加载gradle 面板上的刷新按钮 2.重置缓存 3.删除.idea文件 4.删除out文件、删除.build文件 5.重新拉取项目，更换代码文件目录 6.重装idea 7.清gradle缓存 gradlew build --refresh-dependencies ...
09:41:58.206 [main] ERROR org.springframework.test.context.TestContextManager - Caught exception whi
最新发布
weixin_45714001的博客
01-13 501
避坑，一定要把扫描文件写到距离文件最里边的目录，不然如果junit4与junit5中有相同文件名，不知道扫描的是哪一个。①检查安装依赖是否有问题。
Gradle依赖包的spring依赖
10-31
当我们谈论"Gradle依赖包的spring依赖"时，我们关注的是如何在Gradle项目中配置和管理与Spring框架相关的依赖库。 Spring框架是Java开发中的核心组件，它提供了依赖注入（DI）和面向切面编程（AOP）等关键特性，...
spring gradle依赖 .gradle文件
06-02
总结起来，"spring gradle依赖 .gradle文件"是指使用Gradle作为构建工具来管理Spring框架项目的依赖，并且强调了".gradle"目录在Gradle工作流程中的重要性，包括Gradle Wrapper、守护进程和缓存机制。在Eclipse中...
spring4.0.4jar及其它依赖包
06-01
在实际开发中，正确配置这些依赖包至项目的类路径或Maven/Gradle构建系统中是至关重要的。这将确保Spring框架和其他相关库能正常工作，避免出现“找不到类”或“版本冲突”等问题。对于初学者来说，学习如何管理和...
struct+spring+hibernate依赖包大全
06-15
这个"Struct+Spring+Hibernate依赖包大全"提供了这三个框架最新版本所需的全部jar包，使得开发者能够快速搭建一个完整的SSH集成开发环境。 1. **Struts**： Struts是Apache组织开发的一个开源MVC框架，它为Web应用...
【译】Gradle 的依赖关系处理不当，可能导致你编译异常
weixin_33961829的博客
04-03 242
文章 | Ashesh Bharadwaj 翻译 | 承香墨影 授权 承香墨影 翻译、编辑并发布 在 Android Studio 中，Gradle 构建过程对于开发者来说，很大程度上是抽象的。作为一个新的 Android 开发者，我们第一次遇到 Gradle 通常是在 build.gradle 文件中添加一个远程依赖项。 让我们看看如何阅读 Gradle 依赖关系树，并解决与依赖关系有关的...
spring-test依赖中MockMultipartFile冲突问题
zyx254663zyx的博客
12-24 6971
file转MultipartFile的时候会用到MockMultipartFile 当你导入spring-test依赖的时候 会跟某些依赖冲突（暂未找到具体是哪个冲突） 解决方法 重写一个类去实现MultipartFile接口 直接用MockMultipartFile的源码 public class MultipartFileDto implements MultipartFile { private final String name; private String origi
[Gradle中文教程] Gradle-5.4:依赖-依赖的更新与缓存
ch847808805的专栏
07-21 1655
更新依赖 在执行build、compile等任务时会解析项目配置的依赖并按照配置的仓库去搜寻下载这些依赖。默认情况下，Gradle会依照Gradle缓存->你配置的仓库的顺序依次搜寻这些依赖，并且一旦找到就会停止搜索。如果想要忽略本地缓存每次都进行远程检索可以通过在执行命令时添加–refresh-dependencies参数来强制刷新依赖。 gradle build --refresh-d...
mybatis+spring spring单元测试报错
慢慢来的博客
09-16 780
mybatis 逆向工程 ， 生成 mapper.xml 文件，手动配置一对多关系，服务器运行报错，找不到关联的类，主要是代码写错了
ERROR org.springframework.test.context.TestContextManager 【使用Dubbo框架编写Junit测试类时遇到的坑】
杨大仙
12-20 2856
解决方案： 由于使用的是Dubbo框架，因此在我们确认Junit单元测试环境没有问题的前提下： 首先检查是否开启Dubbo服务； 其次，若测试类编写在消费者consumer模块，则需先检查是否开启提供者provider服务； 启动对应服务即可解决问题。 详细报错信息如下： [main] ERROR org.springframework.test.context.TestContextManager - Caught exception while allowing TestE...
spring boot gradle添加新的依赖
weixin_40775703的博客
03-17 2371
spring boot gradle添加新的依赖 1.在build.gradle中加入依赖： PS：添加jar包依赖最好参考：https://mvnrepository.com/ 例如swagger包依赖语句在:https://mvnrepository.com/artifact/io.springfox/springfox-swagger2/2.9.2 dependencies { compi...
spring security 2.3.0 和 spring core 5.2.6 依赖冲突
06-04
这可能是由于 Spring Security 2.3.0 和 Spring ...也可以使用 Maven 或 Gradle 等构建工具来管理依赖关系，以确保没有冲突的依赖项。如果您需要更具体的帮助，请提供更多的上下文信息，比如您的项目配置和错误日志等。
评论
添加红包

请填写红包祝福语或标题

个

红包个数最小为10个

元

红包金额最低5元

当前余额3.43元 前往充值 >
需支付：10.00元
成就一亿技术人!
领取后你会自动成为博主和红包主的粉丝 规则
hope_wisdom
发出的红包
实付元
使用余额支付
点击重新获取
扫码支付
钱包余额 0

抵扣说明：

1.余额是钱包充值的虚拟货币，按照1:1的比例进行支付金额的抵扣。
2.余额无法直接购买下载，可以购买VIP、付费专栏及课程。

余额充值