On 06/23/2011 05:56 PM, Phil Hagelberg wrote:
Aaron Bedra<[email protected]> writes:
I start with Leiningen because it is simple. I end up on Maven when
Leiningen can't provide what I need. This list includes but is not
limited to:
* Projects that have multiple local project dependencies, all in the
build chain
Have you looked into checkout dependencies? I'd be interested in hearing
more about this particular use case if it's something that checkout deps
don't address.
I haven't looked at that quite yet.
* Projects that have native (JNI) code that need to be built and are a
dependency of the project
Hah; I have been looking for people to test the new native deps support
in Leiningen for weeks. Where have you been? =)
My native deps problem is the one that I replied to on the list when you
asked for help. It is not just including a native dep, but actually
building it.
* Projects where Leiningen just happens to fall down for some
unexplained reason
It would be great to see bug reports for these cases if it's not too
much trouble.
Yes, we need to start sending stuff in. The only problem is recreating
the bug in a way where we can share the code. It is often times some
strange repl issue that doesn't exist until we are multiple layers deep
in a project. There haven't really been too many random lein bugs in
quite a while though. Most of them had to do with repl but we don't use
that anymore.
I'll try to be more diligent with submitting reports :)
Aaron
--
You received this message because you are subscribed to the Google
Groups "Clojure" group.
To post to this group, send email to [email protected]
Note that posts from new members are moderated - please be patient with your
first post.
To unsubscribe from this group, send email to
[email protected]
For more options, visit this group at
http://groups.google.com/group/clojure?hl=en
