On Fri, Mar 5, 2010 at 2:38 PM, Rick Moynihan <rick.moyni...@gmail.com> wrote: > (1) getting ./config on the classpath so I can keep properties files, json > config, whatever, separate from code and lib
This is actually what the resources/ directory is for. > (2) having more than one kind of tests, in different dirs (e.g. specs, > features) and having their classpaths work through lein. It would be best if this could be handled by plugins rather than specified in every project.clj. Currently the plugin framework doesn't expose the hooks that would be needed for this, but it's definitely on the short list for version 1.2.0. > (3) Managing proprietary libraries and API's that you are developing > or using... Yes you can throw these into your own maven repo, but > then you also need to manage, configure and secure a server (when > working in a team). I think it would be great if it were easy to run your own clojars server. Not only for mirroring purposes (poor ato isn't going to be able to eat the bandwidth bills forever) but also to deal with situations like this. But there may be other valid reasons that nobody has even encountered yet, so I favour having total flexibility anyway. -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
