This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2016-05-10
Channels
- # admin-announcements (4)
- # aleph (1)
- # beginners (29)
- # boot (112)
- # braveandtrue (1)
- # cider (44)
- # cljs-site (1)
- # cljsjs (2)
- # cljsrn (1)
- # clojure (46)
- # clojure-gamedev (3)
- # clojure-germany (1)
- # clojure-nl (1)
- # clojure-norway (1)
- # clojure-russia (20)
- # clojure-sg (2)
- # clojure-uk (14)
- # clojurescript (228)
- # cursive (41)
- # datascript (5)
- # datomic (17)
- # editors-rus (48)
- # emacs (3)
- # flambo (1)
- # hoplon (9)
- # jobs (2)
- # kekkonen (1)
- # lein-figwheel (1)
- # luminus (5)
- # mount (11)
- # nrepl (3)
- # off-topic (7)
- # om (12)
- # onyx (139)
- # other-languages (54)
- # planck (1)
- # proton (17)
- # re-frame (37)
- # remote-jobs (1)
- # rethinkdb (9)
- # ring (2)
- # ring-swagger (6)
- # test-check (1)
- # uncomplicate (8)
- # untangled (2)
hey, so I'm trying to use boot-ragtime and I'm getting this error:
clojure.lang.ExceptionInfo: java.lang.ClassCastException: clojure.lang.PersistentVector cannot be cast to clojure.lang.Named
data: {:file "/tmp/boot.user110641794411431225.clj", :line 39}
java.util.concurrent.ExecutionException: java.lang.ClassCastException: clojure.lang.PersistentVector cannot be cast to clojure.lang.Named
java.lang.ClassCastException: clojure.lang.PersistentVector cannot be cast to clojure.lang.Named
@jethroksy: if you do $ boot foo bar
and you get an error like that with a line number, what you can do is run it again with -v
option like this: $ boot -v foo bar
it's the -b
option that shows the source of the boot.user
namespace that boot generates
it's specific to this: https://github.com/mbuczko/boot-ragtime
(require '[edubot.core]
#_'[mbuczko.boot-ragtime :refer [ragtime]]
'[environ.boot :refer [environ]]
'[mathias.boot-sassc :refer [sass]]
'[seancorfield.boot-expectations :refer [expectations]])
yeah I thought it could be https://github.com/mbuczko/boot-ragtime/blob/master/src/mbuczko/boot_ragtime.clj#L45
It looks like this in ragtime's wiki:
(def config
{:datastore (jdbc/sql-database {:connection-uri "..."})
:migrations (jdbc/load-resources "migrations")})
so I thought passing a string wouldn't work but that doesn't seem to be the problem, and doesn't correspond to the error message I got
the things I make tend to only start working a day after I build it, so I'll probably try again tomorrow and if the issue persists, i'll crate an issue there then
I feel like this is probably easy and I'm just missing some doc somewhere for a builtin - I have 3 css files I want to combine into a single app.css - is there a built in that I could easily join all the CSS together with?
Realizing I should probably just make these imports and use the sass compiler - but still curious about how I'd accomplish the task in boot if I didn't have sass - combining all our random CSS files for plugins into a single file.
@therabidbanana: the usual approach is to write a task like concat
that takes a list of files and puts them in a designated place
Okay, so I'm not missing some built-in option to sift or anything like that - I would need to create my own task?
hi booters. i’m back to working on boot-gae for google appengine. i have a tricky problem i can’t quite figure out. a GAE “modularlized” app is an EAR dir containing one WAR (exploded) per module. i can make it work by hand, but I’d like each module to be an independent project/dependency. so that editing would involve the standard boot watch pom jar install
for the module i’m working on, but then i need a “watch-deps” task so that when a new version of a module is locally installed, it will be copied/exploded to the EAR dir. i don’t think checkout would work for this but i don’t entirely understand the checkout logic so maybe it would. i can write my own task to copy module code to EAR on change, but making the modules real modules (maven artifacts) seems much better. FWIW modules in a GAE app like this can be written in any language supported by GAE. Any suggestions?
@mobileink: have you messed with boot checkout
? seems like what you might need
boot checkout -h
has details
the problem is that the gae devserver forks it's own JVM (I think) and uses a fixed classpath. maybe there's a way with checkout, I'll have to beat on it more.
@mobileink: i recommend the --checkouts option to boot itself in 2.6.0-SNAPSHOT over the checkout
task
but to use checkout I need watch first, no? e.g. boot watch checkout ...
I need to watch the artifact, not the source.
ah, it watches the jars, thats what i need. a key point is that a gae modularized app has no source, it's just an aggregate of other projects. so I want to use the maven coordinates of the module components as the link, to keep things clear and simple. it sounds like 2.6.0 will work for this.
so in effect --checkout tells watch what to watch? then the following task can copy etc. as needed?
if so it sounds like checkout adds another property to fileset items. in addition to INPUT and OUTPUT features, we have a WATCH feature. ?
@mobileink: --checkouts
is a boot option in 2.6.0, not a task
instead of using aether to load a jar onto the classpath, it uses aether to resolve the jar but then unzips it into a directory
@mobileink: you still need to have the dependency in your :dependencies
vector though
the --checkouts
option overrides that, but the :dependencies
still needs to contain the dep
correct, unless you use the uber task or whatever you'd normally use to extract a thing from the classpath
Is there a way at the moment to avoid the Warning version conflict detected
message?
mmm, yes you are right, so maybe the counter-question can be, is there a way to clean up the currently loaded classpath?
would it be difficult to add this? Because I know that pod can achieve that, but sometimes I cannot execute stuff in a pod
for instance boot-cljs
is already executed in a pod
at the moment my boot test
executes both boot-test
and boot-cljs-test
calling set-env!
with the right deps
and of course I have warnings
one is:
Warning: version conflict detected: org.clojure/clojure version changes from 1.7.0 to 1.8.0
Warning: version conflict detected: org.clojure/clojure version changes from 1.7.0 to 1.8.0
yeah maybe I can play with exclusions
and it's weird because my boot env is 1.8.0
, somebody is setting it to 1.7.0
there is one
I also have others:
Warning: version conflict detected: adzerk/env version changes from 0.3.0 to 0.2.0
Warning: version conflict detected: org.clojure/tools.reader version changes from 0.10.0 to 1.0.0-beta1
Warning: version conflict detected: org.slf4j/slf4j-api version changes from 1.7.12 to 1.7.21
Warning: version conflict detected: adzerk/env version changes from 0.3.0 to 0.2.0
Warning: version conflict detected: org.clojure/tools.reader version changes from 0.10.0 to 1.0.0-beta1
Warning: version conflict detected: org.slf4j/slf4j-api version changes from 1.7.12 to 1.7.21
yeah...
I will try to play with :exclusions
btw all this is for a shining brand new boot
template: https://github.com/Lambda-X/lambone
a lot of your work I guess in this template
thanks for that
I put all my boot
knowledge in it, still things can be improved 😄
@richiardiandrea: nice! would you consider adding support for Dirac (jupl/boot-cljs-devtools vs cljs-repl), Garden (boot-garden vs sass) etc or is that out of scope / worthy of a fork ?
@superstructor: sass is already there and I personally prefer it over garden...I am open to tooling (through options)
The cljs Repl is already there with +frontend
option and boot dev
starts both repls in one JVM thanks to pods