(2) Improve the project structure imposed by lein, if it is broken
in some
specific way. (Maybe add a well-known config file for adding
elements to the
classpath?)
People have asked for this, but I have yet to hear a good use case for
it. Mostly it's been requested by people who don't realize how easy it
is to push their own jars to clojars. But if someone wants to
implement it I will not refuse the patch.
I agree that lein+clojars is good enough for lib dependencies. My two
use cases so far are places where the classpath needs to point to
something other than outside libs:
(1) getting ./config on the classpath so I can keep properties files,
json config, whatever, separate from code and lib
(2) having more than one kind of tests, in different dirs (e.g. specs,
features) and having their classpaths work through lein.
Stu
--
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
