>
> 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.
>
That's good.
> I guess my main reason for tying lein-cljsbuild to a specific
> ClojureScript release is that not all
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
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
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@googlegro
