This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2016-05-12
Channels
- # admin-announcements (1)
- # aleph (1)
- # arachne (10)
- # beginners (6)
- # boot (81)
- # braveandtrue (3)
- # cider (42)
- # cljs-dev (1)
- # cljs-edn (52)
- # cljsjs (9)
- # cljsrn (9)
- # clojure (62)
- # clojure-austin (1)
- # clojure-belgium (11)
- # clojure-berlin (2)
- # clojure-gamedev (2)
- # clojure-greece (1)
- # clojure-russia (73)
- # clojure-uk (98)
- # clojurescript (156)
- # community-development (4)
- # component (3)
- # cursive (30)
- # datascript (10)
- # datomic (17)
- # emacs (5)
- # events (1)
- # hoplon (315)
- # jobs (1)
- # jobs-discuss (3)
- # lein-figwheel (6)
- # luminus (18)
- # off-topic (13)
- # om (130)
- # other-languages (122)
- # re-frame (32)
- # reagent (27)
- # rethinkdb (6)
- # ring (2)
- # ring-swagger (31)
- # spacemacs (4)
- # untangled (6)
- # yada (30)
what are the common causes of this error?
clojure.lang.Compiler$CompilerException: java.io.FileNotFoundException: Could not locate boot/core__init.class or boot/core.clj on classpath., compiling:(user.clj:1:1)
java.io.FileNotFoundException: Could not locate boot/core__init.class or boot/core.clj on classpath.
@micha: Would it make sense that checkouts would use the version from normal dependencies? Now the dependency version needs to be set both in checkouts and dependencies props.
I don't know, I just checked boot help
which says SYM:VER
i think checkouts would normally have a different version than the release version in the project deps
perhaps, but I could also update the versions on dependencies
I was thinking I could just add checkouts for a few libraries to build.boot so it would be always enabled
When I enabled checkouts from CLI without version it downloaded some older versions, but I'm not sure which version it finally used
and defining checkouts in set-env! without versions doesn't seem to work
Is there something like https://github.com/xsc/lein-ancient for boot?
@slotkenov: @adamfrey: boot show -u
is in core nowadays
@adamfrey: @slotkenov yeah, boot-deps really isn't very useful these days
@martinklepsch: that’s a shame, why is that?
@slotkenov: because boot show -u
exists
@martinklepsch: I see, missed that message from @juhoteperi
so I am trying to use boot-test, and it lists man lines of “Testing [namespace…]"
but it runs 0 tests
nevermind, my test directory was not in :source-paths
well, I fixed that and still nothing
hmmm….
In my template lambone I never set the deps "globally" but I do it in tasks
So boot show -d
does not work for me
Is there a task out there that prints the dep tree from an arbitrary vector?
Or, would it makes sense to add this functionality to show
?
@cpmcdaniel: with boot show -f
you can dump your classpath
Maybe it can give you a better insight
@slotkenov: try boot show -u or -U to also include snapshot versions
@edannenberg: yes, I’m using that now, thanks
@slotkenov: oh, just saw it was already answered, still getting used to slacks way of displaying history ><
@edannenberg: oh, forgot to scroll down? np
@slotkenov: yea, not the first time that tripped me up either lol
when i specify the :ws-host option to reload task, the client browser still tries to connect to localhost AND the wrong port?
ws-host should change the address
I should probably merge a PR to add ws-port option
@juhoteperi: seems browser connects okay, but when I cider-connect, I get the following:
I'm not exactly sure what weasel does, but probably my setup: emacs: localhost, boot running on remote host serving up cljs, browser on localhost requesting remote site.
cljs-repl also has options to set ws-host etc.
@juhoteperi that helped some, but I wonder why the connection is refused.... I can see that port 41787 is indeed open and listenning
Anyone know if s3-wagon-private supports server side encryption? Looks like it doesn't.
Has anyone had this warning, its harmless of course
[1;33mWarning: version conflict detected: org.clojure/clojure version changes from 1.2.0 to 1.8.0
[m[1
@hlolli: should go away if you pin clojure explicitly
I already have BOOT_CLOJURE_VERSION=1.8.0
in boot.properties and [org.clojure/clojure "1.8.0"]
in dependencies. 😕
@hlolli: if you do boot show -p
maybe that sheds some light.
[✔] org.clojure/clojure
✔ 1.8.0
org.clojure/clojure
✘ 1.2.0
org.clojure/tools.nrepl
Now its
:dependencies '[[org.clojure/clojure "1.8.0"]
[org.clojure/tools.nrepl "0.2.12"]
[local/csnd6 "6.7"]]
Of course everything works and I've never been bothered by warning, just for my ego since I'm planing to show this code to other people soon 🙂
@hlolli: maybe you have a tools.nrepl dependency in ~/.boot/profile.boot
?
Da liegt der hund in der grabe
(deftask cider "CIDER profile"
[]
(require 'boot.repl)
(swap! @(resolve 'boot.repl/*default-dependencies*)
concat '[[org.clojure/tools.nrepl "0.2.12"]
[cider/cider-nrepl "0.10.0"]
[refactor-nrepl "2.0.0-SNAPSHOT"]])
(swap! @(resolve 'boot.repl/*default-middleware*)
concat '[cider.nrepl/cider-middleware
refactor-nrepl.middleware/wrap-refactor])
identity)
(require 'boot.repl)
(swap! boot.repl/*default-dependencies*
concat '[[org.clojure/tools.nrepl "0.2.12"]
[cider/cider-nrepl "0.10.2"]])
(swap! boot.repl/*default-middleware*
conj 'cider.nrepl/cider-middleware)
well, updating to cider-nrepl 0.12.0 and removing refactor middleware and refactor does not remove the warning. But if I'm the only one getting this I wouldn't want to jump at blaming boot right away. But if you hear from this again then, you remember I also got this warning 🙂
And since Im having a beer I can have the confidence to post which project Im running excacly https://github.com/hlolli/panaeolus (dont look too much at this code, hehe 🙂 )
@hlolli: i agree, this looks very interesting! i'm looking forward to checking it out later