Chris Truter

The `boot.properties` file is generated using boot itself, can you try the following: `boot -V` `BOOT_CLOJURE_VERSION="1.7.0" boot -V` Perhaps you don't have `boot` installed yet?

Damn, was hoping it was something super simple :wink: Perhaps try this from `boot repl` to get an idea of what the error is: ``` clojure (require '[clojure.java.shell :as sh])...

@martinklepsch perhaps we should remove this `env` variable, since `1.7.0` is the default now anyway

@sonwh98 do you any suggestions to make this more robust?

It was created because `1.6.0` was still popular at the time but wasn't supported, probably could survive without it now. Creating a `boot.properties` file is still best practice though... Perhaps...

Perhaps a `+firebase` option to add _some library_ and make the sample application durable/multi-user? :fire_engine:

Hey ~~Martin~~ Fabio (woah, too many festive beverages) Thanks for the suggestion, I hadn't seen this `replace-task!` macro before - it's pretty groovy. One thing to note is that [`clojure.core/test`](https://clojuredocs.org/clojure.core/test)...

Whoops, didn't mean to close! A clumsy trackpad fumble :stuck_out_tongue_closed_eyes:

Seems like a good newbie task :smile:

Made any progress with this? I'm thinking along the lines of just live loading the plugins at runtime using something like https://github.com/cemerick/pomegranate. If you're wanting to pull plugins from git...