This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2018-09-08
Channels
- # 100-days-of-code (1)
- # announcements (7)
- # beginners (63)
- # cljs-dev (39)
- # clojure (78)
- # clojure-dev (40)
- # clojure-italy (4)
- # clojure-nl (22)
- # clojure-russia (5)
- # clojure-spec (5)
- # clojurescript (60)
- # cursive (8)
- # datomic (6)
- # emacs (1)
- # figwheel-main (53)
- # fulcro (19)
- # jobs-discuss (11)
- # mount (1)
- # off-topic (3)
- # om (1)
- # pedestal (9)
- # philosophy (1)
- # re-frame (19)
- # reagent (4)
- # reitit (5)
- # shadow-cljs (66)
- # tools-deps (64)
i'm having a godless day, and experimenting migrating a lein-based monorepo to gradle
compiling clojure works fine, but cider / nrepl <-> gradle integration is not that great
you could start nrepl from your app (e.g. as a ss/component), then it’s independent from the build tooling
it has considerably better support for large projects with many subprojects that reference each other, among other things.. i'm using the lein-monolith
plugin for quite some time now, but it has its limits
we have multiple projects/libraries. if it’s not a library we start it in it’s own REPL. if it’s a library and I need to make/try a change, I just evaluate the library namespace in the app’s repl. why do you need subprojects?
yeah i do that as well, but i like to use cider-refresh-ns
and have it refresh all checkout dependencies as well
and it's a large clojure project with 4 different services, but some of these needed to be split up because of dependency hell
for dependency hell I made https://github.com/borkdude/boot-bundle
(but if you need to split things up because of dependency conflicts, bundle won’t help)
yeah, that's actually for situations where you can still override some dependencies and then everything works