Your testing revealed accurate information. The general rule is that if a namespace is from one of the cljsbuild :source-path entries, it will be followed recursively. Unfortunately, for namespaces coming out of the classpath, it's not always possible to recurse (e.g. there's no way to list a directory in a JAR). So, since checkouts are just part of the classpath, they will have to be specified as crossovers in fine detail. :(
On Thursday, April 19, 2012 6:16:40 PM UTC-7, Dave Sann wrote: > > Great. > > Do I need to be explicit in naming crossover files. > > what If I have for example > > crossover/a/b/x.clj > crossover/a/y.clj > > can I do [crossover] and get all of these? > > my test says > - yes in the main project - but only to the level immediately below. i.e > picking up crossover/*.clj > - no in checkouts - I have to be explicit here. > > > D > > > On Friday, 20 April 2012 10:23:48 UTC+10, Evan Mezeske wrote: >> >> Yeah, you should be able to avoid having a .crossover or .generic or >> whatever in your namespaces; those are just examples based on my personal >> way of organizing things. >> >> You can put the crossover files wherever you want, as long as they're in >> the classpath (even in a JAR). They don't need to be named specially, or >> anything like that. So if you specified :crossovers [a.b.c], the plugin >> will look throughout the classpath for a/b/c.clj, and will use it as a >> crossover. >> >> On Thursday, April 19, 2012 5:17:51 PM UTC-7, Dave Sann wrote: >>> >>> I finally started take take a look at this. >>> >>> Apologies are due - it does work. I had errors in my tests. >>> >>> I have a question though. >>> >>> Ideally, I don't really want to have .crossover. or .generic. in my >>> namespaces. >>> >>> Is it possible to put crossover/generic files in a completely separate >>> src directory? >>> >>> If not - how hard do you think this would be? >>> >>> Cheers >>> >>> Dave >>> >>> >>> On Saturday, 7 April 2012 13:39:10 UTC+10, Dave Sann wrote: >>>> >>>> I'll take a look >>>> >>>> On Thursday, 5 April 2012 16:34:34 UTC+10, Evan Mezeske wrote: >>>>> >>>>> I haven't used checkout dependencies with lein-cljsbuild myself, but >>>>> my understanding is that lein will put the "checkouts" directory earlier >>>>> in >>>>> the classpath than other dependencies, so things in there will be found >>>>> first. The clojurescript compiler runs inside an "eval-in-project" in >>>>> Leiningen. I would have assumed that the checkout dependencies would be >>>>> available "in-project", but your testing would seem to indicate that >>>>> they're not. >>>>> >>>>> Feel free to open a lein-cljsbuild case for this; I'll be able to help >>>>> investigate in a few days. Of course, if you track down the problem and >>>>> fix >>>>> it, I'd happily accept a pull request! :) >>>>> >>>>> -Evan >>>>> >>>>> On Wednesday, April 4, 2012 8:59:35 PM UTC-7, Dave Sann wrote: >>>>>> >>>>>> Correction - the code does not compile in simple mode and above >>>>>> because the checkouts do not appear to be found. >>>>>> >>>>>> On Thursday, 5 April 2012 13:31:51 UTC+10, Dave Sann wrote: >>>>>>> >>>>>>> Can anyone confirm whether lein cljsbuild can support use of the >>>>>>> "checkouts" directory? >>>>>>> >>>>>>> I have tried this with a simple test. The code compiles without >>>>>>> error but the checkouts dependencies are not included. >>>>>>> >>>>>>> I know that you can jar the cljs files but it is good to be able to >>>>>>> work without doing this for small edits. >>>>>>> >>>>>>> I currently use a modified version of cljs-watch that does this - >>>>>>> but I would like to switch to a more "standard" build path >>>>>>> >>>>>>> If not supported I will add this as an enhancement request. >>>>>>> >>>>>>> Cheers >>>>>>> >>>>>>> Dave >>>>>>> >>>>>>> -- 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
