On Sat, Oct 2, 2010 at 3:36 PM, Michael Ossareh <ossa...@gmail.com> wrote: > In java I'd normally have a conf file somewhere, and that had a range of > issues so I'm wondering if there is something more lispy
Actually it works really well to use the classpath. Leiningen (and presumably other tools) will place test/ on the classpath ahead of src/, but will not include it in jars, so place config that you want to use in production in src/ or resources/ (which also gets included in jars), and place test config files in test/ or test-resources/. The difference is that in Java you would use .properties files, but in Clojure you should just use Clojure maps. Bonus points if you can merge the config files in resources/ vs test-resources/ with the proper priority so only values that are overridden need to exist in the test version. -Phil -- You received this message because you are subscribed to the Google Groups "Clojure" group. To post to this group, send email to clojure@googlegroups.com Note that posts from new members are moderated - please be patient with your first post. To unsubscribe from this group, send email to clojure+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/clojure?hl=en
