-
Notifications
You must be signed in to change notification settings - Fork 3.4k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Gateway MVC conflict with spring-boot-devtools #3199
Comments
Confusingly, the error suggests that |
I'm having the same problem here with Spring Boot 3.2.1 and Spring Cloud 2023 |
I'm having same error even without spring-boot-devtools with Spring Boot 3.2.1 running at Websphere Liberty. Caused by: java.lang.IllegalAccessError: class org.springframework.cloud.gateway.server.mvc.config.GatewayMvcPropertiesBeanDefinitionRegistrar$RouterFunctionHolder$$SpringCGLIB$$0 cannot access its superclass org.springframework.cloud.gateway.server.mvc.config.GatewayMvcPropertiesBeanDefinitionRegistrar$RouterFunctionHolder (org.springframework.cloud.gateway.server.mvc.config.GatewayMvcPropertiesBeanDefinitionRegistrar$RouterFunctionHolder$$SpringCGLIB$$0 is in unnamed module of loader com.ibm.ws.classloading.internal.ThreadContextClassLoader @13054f9c; org.springframework.cloud.gateway.server.mvc.config.GatewayMvcPropertiesBeanDefinitionRegistrar$RouterFunctionHolder is in unnamed module of loader com.ibm.ws.classloading.internal.AppClassLoader @20cbf14) My project is construted composed from 2 maven projects:
|
When I modified org.springframework.cloud.gateway.server.mvc.config.GatewayMvcPropertiesBeanDefinitionRegistrar.RouterFunctionHolder to public in spring-cloud-gateway-server-mvc-4.1.1.jar everythings works correctly. |
Nice. Would you care submitting a PR? |
Describe the bug
when add
spring-cloud-starter-gateway-mvc
andspring-boot-devtools
dependency together, the application fail to startupSample
just use https://start.spring.io/ to add
spring-cloud-starter-gateway-mvc
andspring-boot-devtools
StackTrace
The text was updated successfully, but these errors were encountered: