-
Notifications
You must be signed in to change notification settings - Fork 1.3k
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
(Jubilee 2021.0.0-M1 + 2.6.0-M1) to (Jubilee 2021.0.0-M1 + 2.6.0-M2) The dependencies of some of the beans in the application context form a cycle: org.springframework.cloud.config.server.environment.vault.SpringVaultClientConfiguration #1956
Comments
Can you try 2021.0.0-SNAPSHOT? |
Hello, What kind of magic is that! |
(If I may ask, what is the root cause, and can the fix of this issue be expected for 2.6.0-M3 please?) |
There was a change in Spring Boot Our next Spring Cloud 2021.0.0 milestone will be compatible. You can try using Spring Cloud 2021.0.0-M1 and set |
Hello @ryanjbaxter, As announce today https://spring.io/blog/category/releases "Spring Boot 2.6.0-M3 available now" This is super exciting, thank you Spring Team. Unfortunately, even after bumping to
PLUS
The problem still persists. May I ask what is the correct way please? I was hoping this M3 release would fix the issue. Thank you for your time |
The next Spring Cloud Milestone will address this, until that is released you will need to continue to use the property above. The milestone should be released this week. |
Hello @ryanjbaxter, Thank you for your input. |
A small issue observed after migration.
Disclaimer: I am filing this issue on Spring Cloud Config Server, but if you believe this issue should be for Spring Cloud, or Spring Boot, please let me know, I will close and amend.
Background:
I had a very simple Spring Cloud Config Server application: with version Jubilee 2021.0.0-M1 + 2.6.0-M1. Working fine, very happy.
The M2 got announced here: https://spring.io/blog/2021/08/19/spring-boot-2-6-0-m2-is-now-available
Therefore, I went to do the version bump up to Jubilee 2021.0.0-M1 + 2.6.0-M2 a bit excited!
Unfortunately, after the version bump, application cannot startup, with this error
Fore sure, it is the version bump, as I just change one number in the whole project (revert back to 2.6.0-M1 = work 2.6.0-M2 = does not work)
May I ask what is the issue? Maybe some workaround?
Hope this issue is helpful, thank you for your time.
The text was updated successfully, but these errors were encountered: