This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2017-02-16
Channels
- # beginners (7)
- # boot (63)
- # capetown (1)
- # cider (20)
- # clara (15)
- # cljs-dev (5)
- # clojure (195)
- # clojure-austria (2)
- # clojure-dev (46)
- # clojure-dusseldorf (9)
- # clojure-germany (6)
- # clojure-greece (36)
- # clojure-italy (5)
- # clojure-nl (4)
- # clojure-russia (173)
- # clojure-sg (1)
- # clojure-spec (93)
- # clojure-uk (65)
- # clojure-ukraine (2)
- # clojured (9)
- # clojureremote (1)
- # clojurescript (52)
- # core-async (14)
- # core-logic (5)
- # cursive (21)
- # data-science (8)
- # datomic (60)
- # emacs (83)
- # jobs (9)
- # jobs-discuss (7)
- # juxt (6)
- # klipse (2)
- # leiningen (1)
- # lumo (24)
- # mount (4)
- # numerical-computing (1)
- # off-topic (18)
- # om (37)
- # om-next (5)
- # onyx (13)
- # pedestal (1)
- # perun (44)
- # proton (2)
- # rdf (3)
- # re-frame (24)
- # reagent (4)
- # remote-jobs (3)
- # spacemacs (3)
- # testing (6)
- # vim (10)
- # yada (2)
So what you wrote above is probably working but the new new cider does it differently
And uses the cljs-repl
task
https://github.com/clojure-emacs/cider/blob/master/doc/up_and_running.md#browser-connected-clojurescript-repl-in-boot-project @qqq
If you find problems yes, report it on cider
and I will have a look OK?
@richiardiandrea : will do, thanks!
hello I think I have an error to report in boot-system with the aleph component. it sometimes give an error when it tries to stop
java.util.concurrent.RejectedExecutionException: event executor terminated
clojure.lang.ExceptionInfo: Error in component :web in system com.stuartsierra.component.SystemMap calling #'com.stuartsierra.component/stop
everytime I have to kill the jvm š
can I add a JAR thatās in my filesystem to the classpath?
@anmonteiro you can use this:
boot.user=> (doc boot.pod/add-classpath)
-------------------------
boot.pod/add-classpath
([jar-or-dir classloader] [jar-or-dir])
A corollary to the (deprecated) `add-classpath` in clojure.core. This implementation
requires a java.io.File or String path to a jar file or directory, and will attempt
to add that path to the right classloader (with the search rooted at the current
thread's context classloader).
@micha š thanks so much
Iāve got an substantial annoyance in my cider/boot workflow (boot 2.6.0, [samestep/boot-refresh "0.1.0" :scope ātestā])
1. start boot repl in terminal via boot repl
2. launch a refresh task there (boot-refresh) via (boot (watch) (refresh))
3. connect to repl from cider
so far so good, everything works as expected until I save a file which produces a compile time error:
4. make a change that breaks compilation, save
5. observe irrelevant stack trace in terminal where boot is running
java.lang.IllegalStateException: Can't set!: *e from non-binding thread
...
clojure.tools.namespace.repl/print-and-return/invokeStatic repl.clj: 22
clojure.tools.namespace.repl/print-and-return repl.clj: 20
clojure.tools.namespace.repl/do-refresh/invokeStatic repl.clj: 96
clojure.tools.namespace.repl/do-refresh repl.clj: 82
clojure.tools.namespace.repl/refresh/invokeStatic repl.clj: 145
clojure.tools.namespace.repl/refresh repl.clj: 128
...
samestep.boot-refresh/eval572/fn/fn/fn/fn boot_refresh.clj: 14
...
clojure.core/apply/invokeStatic core.clj: 646
clojure.core/with-bindings*/invokeStatic core.clj: 1881
clojure.core/with-bindings* core.clj: 1881
...
samestep.boot-refresh/eval572/fn/fn/fn boot_refresh.clj: 13
boot.task.built-in/fn/fn/fn/fn built_in.clj: 167
boot.task.built-in/fn/fn/fn/fn/fn/fn built_in.clj: 348
boot.task.built-in/fn/fn/fn/fn/fn built_in.clj: 348
boot.task.built-in/fn/fn/fn/fn built_in.clj: 345
boot.core/run-tasks core.clj: 938
boot.core/boot/fn core.clj: 948
clojure.core/binding-conveyor-fn/fn core.clj: 1938
does somebody know how to make boot display the actual compilation error here?It is possible to get a relevant exception with cider (by evaling the last saved buffer), but itās a pain
I'm using boot/cljs . I don't want the js files ot get sent ot "./out" -- I want them sent to "../build/out" (where "." = dir where build.boot resides) I'm looking at (doc cljs) but don't see the option. How do I tell the compiler to put the output at "../build/out" instead ?
> NOTE that the CLJS compiler's :output-to and :output-dir options will be overridden by the cljs task. These options are determined by the name and location of a .cljs.edn. By default the cljs task will automatically create a main.cljs.edn file in the root of the fileset, which will result in a main.js in the root of the output directory.
In our dev task when I change a server side .clj
file, our ClojureScript gets reloaded which triggers an http request and this evaluates the touched .clj
file. How do I get cljs to reload only when a client side file has been touched?
I think you're on the right track. Worst case, you could make your own watch task and use fileset diff stuff directly
I want to make this for out big cljs app too. The clj doesn't need refresh because we're using wrap-reload ring middleware
Yeah. I think only-by-re is handy when there is some cljs you don't want to recompile
I used it recently to not reload web workers
I suspect it would be more of a watch task thing
When I run boot I get an error. It says it's downloading boot.jar and then it fails with unknownhostexception: http://github.com. I configured our corporate proxy with BOOT_JVM_OPTIONS, but it seems to be ignoring it.
Any ideas?
is the proxy used for DNS queries?
I made some progress. Boot on Windows ignores environment variables and boot.properties, but boot.l4j.ini works.
Now, apparently, my proxy has an invalid SSL cert :(
@qqq what I do is to append a sift
task at the end of the pipeline
Filtering away .out
or renaming it
Where does boot store libraries that it downloads for your project?
Is it just in ~/.boot/cache
ah awesome
@richiardiandrea : sift definitely would work; however, I already have a (target) so I just hijacked that to put it elsewhere
any suggestion what to debug when I see an exception for Multiple jar entries match: .*/pom.xml
after trying to boot push
an uberjar?
@uwo had the same problem and I solved by specifying :project
. It maybe happens because of the many pom.xml
in the uberjarring, but @micha might know more