I wanted to play with Stuart Sierra's lazytest[1] using Vimclojure.
lazytest depends on clojure-1.2.0-SNAPSHOT (so it says in pom.xml),
and my Vimclojure (compiled against an older clojure version) doesn't
work when launched with clojure-1.2.0-SNAPSHOT on the classpath.
I tried to compile Vimclojure with clojure-1.2.0-SNAPSHOT, but the
latest release fails to compile with a NoSuchMethodError. I then tried
to compile the latest Vimclojure source code[2], but it looks like it
needs to be built with gradle. I downloaded gradle 0.8[3] and ran
`gradle :build` in the Vimclojure source directory, but that fails
because the cojure plugin for gradle is not available.
Could someone help me out? How can I get Vimclojure running with
clojure-1.2.0-SNAPSHOT? Every time I try to play with the latest
Clojure, Vimclojure doesn't want to play along, and I start to go down
this rabbit hole of dependencies and build systems... I'm new to the
whole Java ecosystem, so take it easy on me :P
Thanks much!
Mike
[1] http://github.com/stuartsierra/lazytest
[2] http://bitbucket.org/kotarak/vimclojure/
[3] http://www.gradle.org/
On Mar 9, 3:49 pm, Mike Mazur <mma...@gmail.com> wrote:
> I tried to compile Vimclojure with clojure-1.2.0-SNAPSHOT, but the
> latest release fails to compile with a NoSuchMethodError.
Can you be more specific on the failure? What method is tried to be
called on which object?
I have VC running on all clojure and contrib versions from 1.0 to 1.2-
master-SNAPSHOT for different projects. So I'm surprised people have
trouble with it. (The only gotcha is at the moment that 1.0 doesn't
have clojure.stacktrace. This will be (hopefully) fixed in the next VC
release. Which will also don't require recompilation for different
clojure versions.)
Sincerely
Meikel
On Tue, Mar 9, 2010 at 22:55, Meikel Brandmeyer <m...@kotka.de> wrote:
> On Mar 9, 3:49 pm, Mike Mazur <mma...@gmail.com> wrote:
>
>> I tried to compile Vimclojure with clojure-1.2.0-SNAPSHOT, but the
>> latest release fails to compile with a NoSuchMethodError.
>
> Can you be more specific on the failure? What method is tried to be
> called on which object?
As I went back to re-run ant to get the detailed error, it occurred to
me that I should probably recompile from scratch. Sure enough, running
`ant clean` followed by `ant` resulted in a successful compile.
I guess it's getting quite late for me :) Time for some sleep.
Thanks for the quick reply Meikel!
Mike