This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2015-10-26
Channels
- # admin-announcements (1)
- # beginners (167)
- # boot (117)
- # boulder-clojurians (1)
- # cbus (1)
- # clara (3)
- # clojure (87)
- # clojure-conj (2)
- # clojure-japan (2)
- # clojure-russia (23)
- # clojure-spain (3)
- # clojure-za (2)
- # clojurescript (184)
- # community-development (8)
- # core-async (7)
- # core-matrix (4)
- # cursive (36)
- # data-science (74)
- # datascript (3)
- # datomic (171)
- # events (6)
- # hoplon (83)
- # ldnclj (5)
- # ldnproclodo (1)
- # lein-figwheel (2)
- # leiningen (19)
- # liberator (2)
- # off-topic (5)
- # om (227)
- # onyx (5)
- # re-frame (142)
- # reagent (4)
- # yada (5)
@micha: i wonder about cells for wrapping the FS states
well, ref-backed cells
oh sweet
does it perfs?
hi, in case anyone is interested: https://jarkeeper.com now supports boot projects. See https://jarkeeper.com/hashobject/perun
^ this is awesome 🎉 @juhoteperi boot watch all-jars
with partial rebuilds is going to be a thing!
@martinklepsch: Would be useful it dependencies could be passed to pom task
@martinklepsch: Would remove one reason for with-env etc.
And instead of using with-env/with-dir it would be possible to select the files using sift include
@juhoteperi: you still want dependencies on classpath for aot though
Yeah but for development the classpath could contain dependencies for all modules
I think the issue with using plain sift would be mostly that you cannot go back to the original fileset so you can pass it to following tasks?
@micha: GPG PR could also use review, it should be ready now
a cool thing about the new binary is that you can run any version of boot with it, back to boot 2.0.0
@micha: that sounds great. can head.sh
get deleted?
@martinklepsch: we still use head.sh
to build boot.sh
i made the loader a java program instead of a shell script because this way it has no external dependencies
@micha: looking at the Makefile I don’t see it being used?
@micha: we’re very close to being able building everything with boot
what do you all think about adding something like with-scope
to the built-in tasks? https://github.com/boot-clj/boot/compare/boot-builds-boot#diff-0a1425bd66240468daf4c256a411ce75R125
seems like the right ratio between useful & complex
lol sorry for the noise
Someone ideas what could make the build fail here? https://travis-ci.org/boot-clj/boot/builds/87538853
@pandeiro: Hey there, I think I may have found a solution for https://github.com/pandeiro/heroku-buildpack-boot/issues/3
@pandeiro: Although now it fails installing the latest boot.sh. I'll investigate that as well to see if I can get the whole thing to work before I send a pull request.
Ok. I was looking for an easy way to deploy a web app built via boot. I don't even care if it's heroku. Are there other alternatives?
@jannis: digitalocean and uberjar are pretty handy. also dokku could work nicely with boot I guess
i think @alandipert deployed a web app to heroku this morning
@martinklepsch: Dokku would be cool but I'd have to bring my old vServer up to date first, I guess. 😉 And DigitalOcean have no free option. This is just for a small demo project.
@jannis: you can use boot's web and war tasks to make a .war you can easily deploy to heroku
@alandipert: Cool. Are there any instructions on how to do that anywhere?
@jannis: https://github.com/tailrecursion/hoplon-castra-template/blob/master/src/leiningen/new/hoplon_castra/build.boot#L44-L51
@jannis: combine with https://devcenter.heroku.com/articles/war-deployment#deployment-with-the-heroku-toolbelt
@alandipert: Sweet, thanks
@martinklepsch: boot build?
for 2.4 you mean?
@micha: I don’t know why we should hold of stuff. Also smaller changeset will make troubleshooting easier.
but please tell me some ideas why the build fails: https://travis-ci.org/boot-clj/boot/builds/87538853 😄
me neither. build works locally. and aether code is unchanged.
wait ignore me. seems it must be some issue with my rebasing skills it now fails too for me
@micha: lol. https://github.com/boot-clj/boot/commit/0657eb6449c834fa60a188e873a069ba35cfab43
@micha: it really is the clojure 1.6 > 1.7 update
I guess the issue is that in aether there is 1.6 with :scope “compile”
and in pod its with :scope “provided”
— probably compile overrides the provided bit
@martinklepsch: can you update homebrew please?
testing it out
@micha: so did I understand right that the new boot.sh kind of acts like a version manager as well? i.e. I can run any version of boot I want?
@micha i installed 2.4 and first invocation downloaded stuff
but now it exits with status 254
do lein new hoplon app && cd app && boot dev
ah there's a boot.properties in here
@alandipert: it's something in the build.boot
yeah i'm bisecting
it's in the set-env
@micha: ok i think it's related to bringing in versions of clj... boot -d org.clojure/clojure:1.3.0 repl
clojure.lang.ExceptionInfo: loader constraint violation: loader (instance of java/net/URLClassLoader) previously initiated loading for a different type with name "clojure/lang/Compiler$Expr"
i concur
if i set-env from an established repl, it works
@micha: anything that could require a new binary release?
@micha: I’ll close the homebrew PR for now. let me know when I should reopen
ok thanks @martinklepsch