title: Is it ok to put configuration files in JARs?
body: <p>We are having a debate at my office around what can and cannot go in a JAR file. It has been suggested that it is poor form to have anything that is not a .class file go into a JAR. We currently have some XML configurations for Ibatis/etc, some property files.. the usual. However, there is a push to extract all such files from JARs  and put them onto the local file system of each deployment machine. Does this sound reasonable?</p>