The namepace resolution issue vanished after upgrading Cursive and re-opening the project after deleting the IntelliJ artifacts in it. Checkouts namespacing is recognized as well, and checkouts src directories are nicely marked as such.
However, when loading the file in the REPL I get a "Could not locate menthy/utils_java/jdbc__init.class or menthy/utils_java/jdbc.clj on classpath" exception for calls to the checkout project(s). On Tuesday, November 5, 2013 7:51:00 AM UTC+1, Colin Fleming wrote: > > Hi Niels, > > I've just released Cursive 0.1.05 which fixes this issue. Documentation > for the Leiningen support is > here<http://cursiveclojure.com/userguide/leiningen.html>. > Basically you should be able to just import your project wholesale and it > will automatically work out all the dependencies. Checkout dependencies are > also transparently supported for interop with other tools. > > Let me know if it works for you, and I'd be interested to know more about > your namespace resolution problems too. Feel free to drop me a mail at > cur...@cursiveclojure.com <javascript:> if you'd rather send it off-list. > > Thanks, > Colin > > > On 2 November 2013 04:44, Niels van Klaveren > <niels.va...@gmail.com<javascript:> > > 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 clo...@googlegroups.com<javascript:> >> Note that posts from new members are moderated - please be patient with >> your first post. >> To unsubscribe from this group, send email to >> clojure+u...@googlegroups.com <javascript:> >> 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+u...@googlegroups.com <javascript:>. >> 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.
