Re: Bug 235 ("clojure...classpath") seems open to me (on 3.12-SNAPSHOT)

Philip Aston <[email protected]> Sun, 13 Jul 2014 10:11:24 +0100
Newsgroups gmane.comp.java.grinder.user
Message-ID <[email protected]>
Thanks for the report. I've replied on the ticket:
https://sourceforge.net/p/grinder/bugs/235/#c47a

On 12/07/14 02:05, Jameson Quinn wrote:
>
> Bug 235 <https://sourceforge.net/p/grinder/bugs/235/> seems alive to me:
>
>
>     I'm trying to get meteor-load-test working and I think I'm still
>     seeing this bug on the latest code. Here's what I've done:
>     -installed meteor-load-test (on OSX with homebrew)
>     -manually deleted all the 3.11-related files/dirs from ~/.m2/...
>     -pulled and built 3.12-SNAPSHOT
>     -edited meteor-load-test/project.clj to refer to 3.12-SNAPSHOT
>     -run an agent and a console, and pressed "start workers"
>     and here's the error I get:
>     ...
>     SLF4J: Actual binding is of
>     type[ch.qos.logback.classic.util.ContextSelectorStaticBinder]
>     2014-07-08 10:30:42,016 ERROR worker-bootstrap: Error running
>     worker process
>     net.grinder.engine.common.EngineException: Clojure is not on the
>     classpath
>     at
>     net.grinder.scriptengine.clojure.ClojureScriptEngineService.createScriptEngine(ClojureScriptEngineService.java:56)
>     ~[grinder-core-3.12-SNAPSHOT.jar:na]
>     ...
>
>
> I realize that there's probably something basic I'm missing. But since
> just getting this far meant fiddling with at least three tools I've
> never used before (ant, maven, and leiningen), I'm not up to seeing
> the mistake. Can anyone help me here?
>
> Thanks a lot,
> Chema 
>

------------------------------------------------------------------------------

_______________________________________________
grinder-use mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/grinder-use