You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
For English only, other languages will not accept.
Please pay attention on issues you submitted, because we maybe need more details.
If no response anymore and we cannot make decision by current information, we will close it.
Please answer these questions before submitting your issue. Thanks!
The text was updated successfully, but these errors were encountered:
linghengqian
changed the title
spring.factories should remove the AutoConfiguration classspring.factories should remove the AutoConfiguration class or add new file
Sep 14, 2022
Feature Request
For English only, other languages will not accept.
Please pay attention on issues you submitted, because we maybe need more details.
If no response anymore and we cannot make decision by current information, we will close it.
Please answer these questions before submitting your issue. Thanks!
Is your feature request related to a problem?
Describe the feature you would like.
spring.factories
should remove theAutoConfiguration
class and keep the others. The feature thatspring.factories
includesAutoConfiguration
is deprecated in SpringBoot OSS 2.7.0 and removed in Springboot OSS 3.0.0. Refer to Remove spring.factories auto-configuration support spring-projects/spring-boot#29699 .Refer to https://github.com/apache/shardingsphere/blob/master/shardingsphere-jdbc/shardingsphere-jdbc-spring/shardingsphere-jdbc-core-spring/shardingsphere-jdbc-core-spring-boot-starter/src/main/resources/META-INF/spring.factories .
If
spring.factories
is not changed, it will directly break the integration of ShardingSphere SpringBoot Starter and SpringBoot OSS 3.0.0-M5.If the project needs to retain support for SpringBoot OSS <= 2.6, it needs to use the processing method of Migrate to new Spring Boot auto configuration introduced in spring bo… remkop/picocli#1778 .
The text was updated successfully, but these errors were encountered: