This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2018-10-17
Channels
- # 100-days-of-code (5)
- # announcements (13)
- # beginners (98)
- # boot (19)
- # cider (10)
- # cljdoc (32)
- # clojure (142)
- # clojure-dev (37)
- # clojure-italy (3)
- # clojure-nl (2)
- # clojure-spec (30)
- # clojure-uk (18)
- # clojurescript (28)
- # cursive (8)
- # datomic (25)
- # duct (18)
- # editors (5)
- # emacs (39)
- # events (4)
- # figwheel (7)
- # figwheel-main (5)
- # fulcro (38)
- # graphql (19)
- # jobs-discuss (1)
- # jobs-rus (7)
- # keechma (1)
- # lumo (47)
- # off-topic (28)
- # om-next (3)
- # parinfer (3)
- # re-frame (18)
- # reagent (37)
- # reitit (8)
- # shadow-cljs (101)
- # specter (7)
- # tools-deps (8)
- # vim (1)
@hmaurer reply has a bug in it, it can be safely ignored. I think there's a patch to fix it already.
@seancorfield when using boot-tools-deps with -B
and the pom
task I'm seeing that the generated pom's dependencies all have scope "compile"
— is that intentional/expected?
I'm using boot to package a jar of a deps.edn
based app: boot -d seancorfield/boot-tools-deps deps -B pom -p cljdoc -v 0.1.0 jar install
@martinklepsch it's not "intentional" in terms of boot-tools-deps -- pretty sure that's the default scope for tools.deps itself? As for expected...
If you're using deps.edn
why not use a packager like depstar or cambada or pack?
because I couldn't get any of them to make a regular (i.e. non uber) jar
but I'm probably overthinking this. I should just package stuff as a zip file and run clj
😄
Cambada's has plain JAR support https://github.com/luchiniatwork/cambada#packaging-as-a-jar
I tried the cambada packager but there even the plain jar does AOT which I found confusing (and couldn't figure out how to disable)
@martinklepsch use packs skinny jar mode, theres a param for making it only dump out the current project.
Or are you still looking for an extra feature on top? I'm happy to assist you with this 😊
@dominicm I saw that in the sources but it’s not mentioned in the readme is it? I’ll take another look
I’ve been thinking about just packaging it all in a tar file haha 😆
Isn't it? I just have failed to push/write documentation. I'm gaining a reputation for this 😁
In any case I need to set up some build step where JS is bundled and all that and so looking for something to do that. The jar requirement isn’t too strict but I thought it would be nice to just run cljdoc in prod by depending on a regular jar and running some main
Somewhat related to the recent discussion: as of this morning, our entire CI pipeline (including SQL migrations, JAR building and deployment to servers) runs on clj
/`deps.edn` for most of our projects -- previously that was all on Boot.
This bug was killing us https://github.com/boot-clj/boot/issues/715
(as well as the 2.8 series of releases being both fairly buggy and including breaking changes)