Right, this is still a little messy - this is actually something I'll be working on this week. I fixed up the existing support which wouldn't allow multiple modules at all (or at least would throw exceptions when Aether couldn't resolve the dependencies), but it's still not smart about adding one module to the classpath of another, sorry. I'll try to fix this in the next build.
The require :as alias and require :refer should definitely be working, could you let me know what your ns form looks like? Maybe drop me a mail at curs...@cursiveclojure.com rather than on the list. I'd be interested to know what your multi-project lein project looks like, too. Thanks! On 2 November 2013 05:24, Niels van Klaveren <niels.vanklave...@gmail.com>wrote: > I don't think it's the way to do it, because the checkouts /src directory > gets unmarked when the project is loaded anew after an IntelliJ restart. > > > On Friday, November 1, 2013 4:44:49 PM UTC+1, Niels van Klaveren wrote: >> >> The release notes mention that working on multiple Leiningen projects has >> been improved, but how to get it working ? >> I wondered if there's a preferred way to work on multiple Leiningen >> projects, so changes in one are reflected in the other. >> >> - Leiningen has the option to work with the checkouts directory >> containing a simlink (linux) / junction link (windows) to the directories >> in question >> - CounterClockWise has the option to add the other project to the project >> build path >> >> I got things working by using the checkout directory / junction link >> method, and in Cursive marking the checkout source directory as a Source >> Root. >> Is this the intended way to do it, or is there another way ? >> >> Another thing I noticed is that require :as alias and require :refer >> aren't picked up, and all aliased / referred function calls are marked as >> "cannot resolved be resolved" warnings. >> Any way I can get rid of those ? >> > -- > -- > 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 > --- > You received this message because you are subscribed to the Google Groups > "Clojure" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to clojure+unsubscr...@googlegroups.com. > For more options, visit https://groups.google.com/groups/opt_out. > -- -- 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 --- You received this message because you are subscribed to the Google Groups "Clojure" group. To unsubscribe from this group and stop receiving emails from it, send an email to clojure+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
