-
Notifications
You must be signed in to change notification settings - Fork 40.5k
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
Move away from spring.factories for auto-configuration imports #29698
Comments
Due to |
Hi @philwebb, Can you explain the idea of setting |
@haydin505 I see you also asked this on Stack Overflow where someone is already trying to help you. Please don't ask the same question in multiple places at the same time as it just wastes people's time. |
@wilkinsona I have researched the issue, traced design and development, then I asked direct question to the author of the issue. In other words, here I’m trying to gather information from the creator. On the other hand, in Stack Overflow I created a thread to discuss and realize new perspective. Hence, they are not duplicate, both questions has their own meaning. Thank for the feedback though. |
@haydin505 It's quite time consuming for us when people ask questions here and we specifically ask people not to do it. It's worse when there is a question on stackoverflow.com and not even a reference to it since we may expend effort here when someone else is already helping. |
@philwebb Sorry for the inconvenience. For later cases I will only create questions on Stack Overflow and not ask anything on GitHub. |
Thanks @haydin505! FWIW I posted an answer that I hope helps. |
technical debt: annotate auto configuration classes with spring-boot's `@AutoConfiguration` instead of spring's `@Configuration`. `@AutoConfiguration` was introduced in 2.7 with the idea to mark all auto-configurations with its dedicated annotation and move away from spring.factories for auto-configuration imports in 3.0 as described in this [Github issue](spring-projects/spring-boot#29698).
Using
spring.factories
to find auto-configuration classes is causing problems with our native work. We initially used it because the code was already available, but we want to offer an alternative in 2.7 and stop usingspring.factories
for auto-configuration in 3.0.The following required tasks have been identified:
spring.factories
for auto-configuration.spring.factories
and the new entries.@AutoConfiguration
annotation which is meta-annotated with@Configuration
. The new annotation will defaultproxyBeanMethods
tofalse
.buildSrc
to read the new fileThe following nice-to-have tasks have been identified:
sed
)We will need to retain
spring.factories
support for the life of 2.x because Spring Cloud will not be able to migrate to a new system (since it supports 2.6)The text was updated successfully, but these errors were encountered: