About Daniel Bryant
Quite a common use case when developing a Spring application is that you want to have multiple versions of configuration properties depending on where you are deploying to, for example, database URLs or feature flag may be environment specific on dev, qa, production etc.
Like most Spring development tasks, there are several way to solve the problem. My preference is based on the following assumptions and preferences:
- We create a default configuration properties file (e.g. ‘appConfig.properties’) and package this within the deployable artifact (JAR or WAR etc)
- This file will contain a sensible set of default ‘baseline’ properties that the application requires to run successfully
- This default configuration file will typically be used for development purposes i.e. the appConfig.properties included within the application code will allow the application to work ‘out of the box’ on a well configured local development box
- We are using Maven to package our application, and therefore we place the appConfig.properties file in the root level of the src/main/resources directory – this doesn’t mean you have to use Maven, but you will have to ensure that your application packaging process includes the properties files in a location that is on the classpath
Source : http://www.javacodegeeks.com/2013/07/overriding-a-packaged-spring-application-properties-file-via-an-external-file.html
