Remove Location Attributes from @ConfigurationProperties
What are the alternatives?
I used it as before.
@ConfigurationProperties(locations = "a.yml")
Same problem: we have hundreds of configuration keys in several yaml files, each of which is conveniently mapped to pojo, which we introduce into our beans business logic.
The best thing I could do to upgrade to Spring Boot 1.5 and at the same time keep our production application working without much refactoring is described here: http://fabiomaffioletti.me/blog/2016/12/20/spring-configuration -properties-handle-deprecated-locations /
Or, if this does not work for you, you can try this method, which is easier, even if you need more refactoring (remove the @ConfigurationProperties annotation): http://fabiomaffioletti.me/blog/2017/02/09/spring-configuration- properties-locations-deprecation-another-approach /
Source: https://habr.com/ru/post/1014757/More articles:Android allows to restrict INSTALL_REFERRER to play in storage - androidHow can I use readline synchronously? - javascriptCelery & Rabbitmq: WARNING / MainProcess] An unknown message was received and deleted. Wrong destination?!? - GIT experiment - celeryWhere smart contracts are on the blockchain (Ethereum or Hyperledger) - storageFix cleaning action bug in slick dbio effects - scalaIs there any difference between importing {Observable} from 'rxjs / Observable' and import {Observable} from 'rxjs'? - angularSafari mailto: "This site is blocked from automatically creating email." - htmlInstructions AVX512 log2 or pow - x86How to filter data using Spring? - javaHow to pass an argument starting with "//" to a wsh script? - vbscriptAll Articles