This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2022-02-22
Channels
- # announcements (88)
- # autochrome-github (2)
- # babashka (26)
- # beginners (5)
- # biff (2)
- # cider (73)
- # clj-kondo (4)
- # cljsrn (6)
- # clojure (54)
- # clojure-art (3)
- # clojure-europe (73)
- # clojure-germany (5)
- # clojure-new-zealand (1)
- # clojure-nl (13)
- # clojure-norway (16)
- # clojure-uk (8)
- # clojurescript (73)
- # conjure (1)
- # core-async (10)
- # cursive (17)
- # datahike (51)
- # datalevin (21)
- # datomic (4)
- # emacs (2)
- # events (3)
- # fulcro (35)
- # honeysql (6)
- # introduce-yourself (1)
- # jackdaw (3)
- # jobs (1)
- # leiningen (4)
- # lsp (3)
- # malli (17)
- # off-topic (60)
- # other-languages (5)
- # pathom (17)
- # pedestal (3)
- # polylith (19)
- # portal (2)
- # practicalli (1)
- # rdf (14)
- # reitit (3)
- # releases (1)
- # reveal (9)
- # sci (1)
- # shadow-cljs (26)
- # spacemacs (17)
- # sql (4)
- # testing (10)
- # tools-build (6)
- # tools-deps (16)
- # vim (9)
Hello, I'm writing some SPIs for keycloak in clojure, and well I may be nickpicky but I want to create uberjars without the keycloak provided dependancies (since I know they are already included). I can't seem to find any documentation of examples of how I would achieve such behviour with tools.build
? I'm actually using @seancorfield's build-clj to be precise. Any pointers would be much appreciated 🙂
yes that - you can build the basis with whatever aliases or even ad hoc deps you need, and use a different basis for compiling vs uberjar'ing. This might not be easy to do through build-clj, I would just use tools.build directly
Agreed. If you need a different basis for compilation and for uberjarring, then you'll need the low-level control of tools.build
directly @nicolas.estrada938 -- build-clj
assumes the same basis for both compile-clj
and uber
under the hood.
Thanks for the clarification, I'm going to postpone making my uberjar as smallest as possible for the moment 😅
depstar
used to support that via a complex set of options to differentiate between compiling and jar'ing but since tools.build
supports that explicitly and it's a "non-default" use case, I didn't see the point in making build-clj
do it.