|
|
Featured White Papers
- Why choose an Open Source BPM?
- 10 FAQs on Business Process Management
- Best Practices for Getting Started with BPM
- Free Your Devs From The Pain Of Java Redeploys
- Increase Velocity 40% by Using JRebel
- What Developers Want: The End of Application Redeploys
- Developer Productivity Report: Java Tools, Tech, Devs, and Data
- Coding with JRebel: Java Forever Changed
- Utilizing Fast Testing to Transform Java Development
- Do You Really Get Classloaders?
- Pragmatic Continuous Delivery with Jenkins, Nexus, and LiveRebel
- Your Next Java Web App: Less XML, No Long Restarts, Fewer Hassles
- Coding with JRebel, Java Forever Changed
- 2012 Developer Productivity Report: Java Tools, Tech, Devs, and Data
Location of properties file
Submitted by somakd on Fri, 07/16/2010 - 04:56.
I am trying to write a File copy program where the source folder and destination folder should be parameterised and will be present in a .properties file. User may change the value at runtime, and the effects should take place without recompilation.
My question dis-regards to this program is - is this a good practice to leave out the properties file outside the jar/war file, so that user can freely edit that ? If so, why ?