-
Notifications
You must be signed in to change notification settings - Fork 38.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
context register @Configuration doesn't respect @Order [SPR-12657] #17257
Comments
Juergen Hoeller commented As of 4.2, we sort all top-level configuration class candidates by Juergen |
Andy Wilkinson commented This change has broken a number of tests in Spring Boot due to its use of A typical test doesn't use the import selector but simply relies on the configuration registration order being honoured. For example:
The ordering here is deliberate. We could change Spring Boot to work around this behaviour change, but Stephane encouraged me to comment here in case there's anything that can be done in the framework . |
Juergen Hoeller commented Why is I'm afraid there's not much we can do about it since the whole point of this change is that Juergen |
Andy Wilkinson commented The I've prototyped a change that introduces |
Matt Benson commented What direction did |
Andy Wilkinson commented We use |
Yanming Zhou commented It seems |
Juergen Hoeller commented I'm not aware of a regression here... We process Juergen |
Yanming Zhou commented I want use |
Juergen Hoeller commented Could you please sketch a test for a case that you'd expect to work but which doesn't? Keep in mind that Juergen |
Yanming Zhou commented Sorry for my fault, It works �fine, my test failed because the key exists in system property and placeholder always resolved with system property. |
Yanming Zhou opened SPR-12657 and commented
according to http://docs.spring.io/spring/docs/current/javadoc-api/org/springframework/context/annotation/PropertySource.html
changing
@Order
of@Configuration
doesn't affect property source overriding.Issue Links:
@Primary
annotation not working when overriding bean definition with classpath scanningReferenced from: commits f5b4e18
0 votes, 6 watchers
The text was updated successfully, but these errors were encountered: