This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2017-02-24
Channels
- # aws (3)
- # aws-lambda (1)
- # beginners (16)
- # boot (36)
- # cider (3)
- # cljs-dev (90)
- # cljsjs (1)
- # cljsrn (27)
- # clojure (240)
- # clojure-austin (1)
- # clojure-berlin (3)
- # clojure-dusseldorf (2)
- # clojure-france (2)
- # clojure-germany (12)
- # clojure-russia (19)
- # clojure-spec (20)
- # clojure-uk (56)
- # clojurescript (218)
- # clojurex (1)
- # cursive (21)
- # datomic (10)
- # events (1)
- # hoplon (18)
- # instaparse (19)
- # jobs-discuss (3)
- # lein-figwheel (3)
- # luminus (3)
- # lumo (14)
- # off-topic (4)
- # om (76)
- # onyx (67)
- # protorepl (12)
- # re-frame (54)
- # reagent (35)
- # ring (2)
- # spacemacs (5)
- # specter (2)
- # sql (11)
- # untangled (144)
- # yada (34)
hmm, how would I add local artifact dependencies in boot?
can't you install the local artifact?
I think better
I have a git clone of the project
I can add a :resource to point to its <project>/target/classes directory
seems dangerous
@cpmcdaniel I think there's a checkouts feature in boot you may be interested in?
actually, I needed the other project’s dependencies as well
fortunately(?) it was a maven project, so a local install did the trick
on a different topic...
I suppose the clojure dependency has to be explicit if you expect it to be included in an uber jar?
Hi, boot allows me to write "one file" executable clojure programs (thanks to shebang boot and (set-env! :dependencies
). However .. is there a way to hook emacs cider as a repl to such program?
you can add a dependency on tools.nrepl and start a repl from within your program
or you might have access to boot’s own repl task
it’s just a function
@cpmcdaniel It requires mofiying the code to work in two modes though (normall running and running a repl). That's a solution, but maybe there's a way to avoid that?
Ok, I guess I can just run a boot repl, hook into it and then evaluate the whole file in t.
^updated to 1.4.3
now provides option to include version file or generate version namespace for use by applications
the option for :develop
just makes a lot of sense!
@richiardiandrea that is technically a breaking change, :no-update
was renamed to :develop
, hope it help's everyone out tho!
Readme now updated with new examples as well 🙂
Thanks!
@adamfrey recently hit a problem with clj-http, strange exception, in trying to fix it i ran across a bug report of yours elsewhere. maybe a clj-http ticket?
no, but i figured out the problem
wasn't sure you ever did
the problem is with potemkin
clj-http depends on a recent potemkin, that's 1.8 compat
but another library of yours was probably also bringing in potemkin, an older non 1.8-compat version
maven was selecting the older, non 1.8-compat version, which blows up clj-http
interesting. Yeah, I’ve avoided that error since. Thanks for the report! Very thoughtful of you
:thumbsup: