Hi,
Have you ever faced a state where the version controller has configuration file and when you work with these configuration files you have to change it locally to suit you however then you need to remember not to commit them to the version controller - which makes clutter, files are updated locally however should not be committed.
The solution:
First try to load this configuration file someconf.${user.name}.properties
Then if not found load the someconf.properties
In this way every user can have his local someconf.myusername.properties and even commit it.
The local conf would be loaded dynamically per machine! per user! so every user will always have his customized configuration files just by checking out all sources from his version controller.
Have you ever faced a state where the version controller has configuration file and when you work with these configuration files you have to change it locally to suit you however then you need to remember not to commit them to the version controller - which makes clutter, files are updated locally however should not be committed.
The solution:
First try to load this configuration file someconf.${user.name}.properties
Then if not found load the someconf.properties
In this way every user can have his local someconf.myusername.properties and even commit it.
The local conf would be loaded dynamically per machine! per user! so every user will always have his customized configuration files just by checking out all sources from his version controller.
Comments