There's some discussion about that going on here: https://github.com/emezeske/lein-cljsbuild/issues/105 .
The user can, AFAIK, specify the org.clojure/clojurescript version in their project, and that will take precedence over the version that lein-cljsbuild depends on. I guess my main reason for tying lein-cljsbuild to a specific ClojureScript release is that not all versions of each are mutually compatible. For instance, lein-cljsbuild used to run builds in parallel, via futures, which worked for a while. More recent ClojureScript versions are not thread-safe, though. Another example is that lein-cljsbuild has occasionally set dynamic bindings from the cljs.closure namespace (to configure things in the compiler that are not otherwise configurable). So those versions of the plugin only work with certain ClojureScript versions. I'm very much open to argument on this topic, though. Pasta knows that I'd like to exit the business of jumping to update the plugin for every compiler release! :) On Saturday, July 7, 2012 8:30:36 AM UTC-7, Stuart Sierra wrote: > > By the way, why does lein-cljsbuild pin to a specific ClojureScript > release? Can that be a project-level dependency decision? > -S > > > On Friday, July 6, 2012 3:49:29 PM UTC-4, Evan Mezeske wrote: >> >> Thanks for the quick turnaround on this release, Stuart! >> >> I just pushed out [lein-cljsbuild "0.2.4"], which will pull in the new >> 0.0-1443 release. >> >> -- 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
