Right, I had a chance to take a look at this - the classpath for the REPL unfortunately doesn't include the source directories of dependent modules. I'll fix that in the next build.
There is a workaround. In Settings->Compiler->Clojure Compiler, enable "Copy Clojure source files to output path". In Settings->Compiler, if you have "Use external build" selected then change the resource pattern for Clojure from !?*.clj to ?*.clj. Then you can build your dependent module manually (for example, by right clicking on it in the project tree and selecting Make Module '<your module>'. That will copy your Clojure files to the output path and they'll be picked up by the REPL then. On 6 November 2013 10:50, Colin Fleming <colin.mailingl...@gmail.com> wrote: > Hmm, there may be some problem with the classpath there - I'll take a look. > > > On 5 November 2013 23:53, Niels van Klaveren > <niels.vanklave...@gmail.com>wrote: > >> 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 if you'd rather send it off-list. >>> >>> Thanks, >>> Colin >>> >>> >>> On 2 November 2013 04:44, Niels van Klaveren <niels.va...@gmail.com>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 >>>> >>>> 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 >>>> >>>> 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. >>>> >>>> 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. >> > > -- -- 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.
