I like Stuart's idea, but I can see those dependency declarations becoming repetitive in any significantly large project. I think there would need to be someway to declare dependencies on a larger scope, perhaps application wide, or some mechanism to describe dependencies for sets of namespaces.
I also think it's worth supporting artifact, group and version information for a given dependency so users, or even an automated tool can easily go out to maven repositories and download them as needed. I think there is a case here for a simple automated tool to use maven repositories to satisfy dependencies, but I am far from an expert in this realm. I think buildr does something similar, but someone can correct me if I'm wrong. -Matt On Apr 14, 12:38 pm, Konrad Hinsen <konrad.hin...@laposte.net> wrote: > On Apr 14, 2009, at 17:17, Laurent PETIT wrote: > > > The problem will then be that the next time I checkout clojure- > > contrib, BLAM I can't compile it because I need to download a jar > > from somewhere on the web ... > > That could be avoided by including the Clojure source in clojure- > contrib, but not add it to the libraries to be precompiled in > build.xml. I suspect that it would even be possible to add specific > compilation targets for libraries that have external dependencies, > but I don't know ant well enough to be certain. > > Note that I am not proposing any dependency management, just separate > compilation targets for "clojure-only" libraries and "depends-on-XYZ" > libraries. For a precompiled jar distribution, that would probably > imply separate jar files. > > 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 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 -~----------~----~----~----~------~----~------~--~---
