-
-
Notifications
You must be signed in to change notification settings - Fork 967
Description
Expected Behavior
I resolved application startup failures caused by several Spring Boot auto-configuration classes. To fix the issue, I disabled the problematic classes by adding them to the spring.autoconfigure.exclude list in my configuration file.
This change allowed two of my applications to start without errors. For components where auto-configuration was disabled (like Redis), I implemented a manual configuration using Groovy/Java.
Here is the configuration I used:
autoconfigure:
exclude:
- org.springframework.boot.autoconfigure.security.oauth2.client.servlet.OAuth2ClientAutoConfiguration
- org.springframework.boot.autoconfigure.security.servlet.SecurityFilterAutoConfiguration
- org.springframework.boot.autoconfigure.security.servlet.SecurityAutoConfiguration
- org.springframework.boot.actuate.autoconfigure.security.servlet.ManagementWebSecurityAutoConfiguration
- org.springframework.boot.autoconfigure.security.oauth2.resource.servlet.OAuth2ResourceServerAutoConfiguration
- org.springframework.boot.autoconfigure.security.servlet.UserDetailsServiceAutoConfiguration
- org.springframework.boot.autoconfigure.task.TaskExecutionAutoConfiguration
- org.springframework.boot.autoconfigure.data.redis.RedisAutoConfiguration
- org.springframework.boot.autoconfigure.reactor.netty.ReactorNettyAutoConfiguration
- org.springframework.boot.autoconfigure.webflux.WebFluxAutoConfiguration
- org.springframework.boot.autoconfigure.webflux.client.WebClientAutoConfiguration
Actual Behaviour
No response
Steps To Reproduce
No response
Environment Information
OS: Linux Ubuntu 24
Java: 24.02
Example Application
No response
Version
7.0.0-RC2
Metadata
Metadata
Assignees
Type
Projects
Status