how to differentiate datasource properties in project structure for DIT UAT SIT and prod in general or for spring framework.
Thanks.
how to differentiate datasource properties in project structure for DIT UAT SIT and prod
Share
Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
how to differentiate datasource properties in project structure for DIT UAT SIT and prod in general or for spring framework.
Thanks.
We currently use Maven as our build and configuration tool. We keep environment specific properties, such as, database URLs, usernames, passwords, etc. in Maven profiles. Maven resource filtering is applied to Spring configuration files to inject environment specific properties.
In the past when I used Ant for building applications, I used to store environment specific properties in separate properties files. Then, Ant token replacement was applied to inject environment specific properties.