On Fri, Sep 7, 2012 at 9:56 AM, Laurent PETIT <laurent.pe...@gmail.com> wrote: > 2012/9/5 Stuart Halloway <stuart.hallo...@gmail.com>: >> I started a wiki page for this: >> >> http://dev.clojure.org/display/design/Never+Close+a+REPL >> >> If you have other REPL-reloading annoyances please add them there. > > Adding new dependencies to my Leiningen project. > > Solved by pomegranate ? > > I think I could add an experimental feature to CounterClockWise so > that whenever the dependencies change, all the new dependencies are > optimistically propagated to open REPLs associated with the project > (maybe asking a user confirmation first). >
Pomegranate can download dependencies and blindly add them to the classpath. It doesn't include any logic to track what jars are already there, so might add the same ones twice on successive calls. Also it doesn't help for moving between dependency trees, which might change a version. This is probably where "optimistically" comes in. A library built on top that can handle this stuff would be awesome. -- 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
