-
Notifications
You must be signed in to change notification settings - Fork 40.8k
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
Starter Autoconfiguration fails creating EnableConfigurationProperties bean #38552
Comments
This looks like the same underlying cause as #38536 (comment). Adding the following to
|
I'd like to leave this open to see if there's more we can do here. It seems like this change is causing issues for a lot of folks and I'd like to discuss it on our next team call. |
That indeed solves the issue. But it's not clear to me what in that sample project requires parameter name retention. Is it the way the tests are written or is it use of |
@roded FTR, runing your sample app with Spring Boot 3.1.5 issues the following warning:
|
@snicoll I actually don't see that warning when running the unit test in Intellij. |
OK, that's a configuration setting of your IDE that is beyond the scope of this issue (what I mean by that is that your current setup means you wouldn't see any warning at all).
I am not sure where the confusion comes from. You're asking to bind |
Understood. Thanks for that @snicoll . Is it possible to explicitly name ctor arguments in a way which will avoid requiring the class information? |
+1 here |
We've added a failure analyzer that should hopefully help folks if they hit this problem. See #38603 |
Hello,
The referenced project has a unit test which works with Spring Boot 3.1.5 but fails in 3.2.0 due to the properties class failing to instantiate. Has anything changed in this regard in 3.2.0?
https://github.com/roded/spring-boot-issue-38552
The text was updated successfully, but these errors were encountered: