title: Is this the best way to keep .properties file out of WAR file?
body: <p>To externalize a .properties file, currently I am keeping it in a file system say
      C:\test\UI\properties
  and I have created a Environment variable $PROP_LOCATION which points to above file location. So whenever I need to change properties, just I go to that location edit properties and refresh the application. It works like a charm.</p>
  
  <p>So is this the best way? Or is there any other way you professionals suggest me to keep properties file out of war file?</p>
  
  <p>Note: The above thing works fine in both unix and windows environment as I have a "if" condition, if one of the environment variable not found I will check for another environment variable.</p>