On 22 Jan 2010, at 07:23, Richard Newman wrote:
* For those who might ask "and what kind of user are you?":
* I keep up to date with Clojure master. I don't use binary releases.
* I fix bugs and make changes in my local Clojure/contrib/third-
party library trees, and I want *all* of my builds to use *those*,
not their own choice of versions. With lein/mvn I have to install a
custom version of those libraries into my repo, then change all of
my libraries to use the custom version. New build = changing every
library's project file again (or overwriting the repo version... not
sure how acceptable a solution that is). With my previous approach I
simply had to overwrite a jar (allowing my VCS to track the old
version).
My needs are pretty similar, which is why I have not adopte leiningen
either.
I typically work on a set of related projects, all of which are under
development at the same time. I don't want anything AOT compiled and I
must be able to specify dependencies that exist only as source code on
my computer and have no version number. So for the moment, I am
managing everything manually; fortunately my projects are small and
few enough for that. I'd love to be able to use leiningen for some of
the tasks, and I hope it will evolve along those lines.
Konrad.
--
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
