-
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
PropertiesMigrationListener wrongly reports property as deprecated #35774
Comments
This indeed looks like a bug. The
returns a non-null match when invoked with e.g. "spring.kafka.producer.ssl.keystore-location". I assume this is because of the relaxed mapping support in However, I can't reproduce that you get those messages two times. Could you maybe provide a small sample which reproduces this double printing issue? |
I see you added 2.7.x milestone, but forgot to mention this (also) happened using Spring Boot 3.1.0 |
I suspect the underlying cause is in Boot 2.7.x too. When we fix that bug there, we forward merge to 3.0.x and 3.1.x. |
This comment was marked as outdated.
This comment was marked as outdated.
This comment was marked as outdated.
This comment was marked as outdated.
This comment was marked as outdated.
This comment was marked as outdated.
This comment was marked as outdated.
This comment was marked as outdated.
because of the relaxed mapping support in SpringIterableConfigurationPropertySource, like "keystore" and "key-store" map to the same relaxed value. valid metadata by `PropertyMapper` Closes spring-projects#35774
With the following configuration:
I get the following message:
But I already changed them to the new one. It's just a warning, but it seems to be incorrect. Also interesting it shows it twice with different property source names.
The text was updated successfully, but these errors were encountered: