This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2018-04-24
Channels
- # architecture (7)
- # beginners (73)
- # boot (4)
- # cider (48)
- # cljsjs (7)
- # cljsrn (27)
- # clojure (206)
- # clojure-boston (2)
- # clojure-italy (21)
- # clojure-nl (8)
- # clojure-spec (7)
- # clojure-uk (94)
- # clojurescript (126)
- # clojutre (7)
- # core-async (3)
- # cursive (7)
- # data-science (1)
- # datascript (4)
- # datomic (6)
- # duct (1)
- # emacs (19)
- # figwheel (1)
- # fulcro (31)
- # graphql (13)
- # jobs (5)
- # jobs-discuss (42)
- # keechma (4)
- # leiningen (10)
- # luminus (3)
- # mount (2)
- # nyc (3)
- # off-topic (37)
- # om-next (3)
- # onyx (45)
- # pedestal (2)
- # re-frame (4)
- # reagent (2)
- # reitit (16)
- # shadow-cljs (118)
- # spacemacs (10)
- # tools-deps (8)
- # vim (20)
phreed14:04:13
Unrealistic because the boot.App does more than just provide data to the tasks? Such as managing all the pods?
phreed14:04:07
Do you know of an example that builds an uberjar https://clojure.org/guides/deps_and_cli#_using_local_libraries ?
alandipert17:04:25
@phreed correct re: pods, boot.App needs to be the entrypoint because it needs to own the classloader before clojure is introduced
seancorfield18:04:02
@phreed There are two uberjar builders for clj
that I'm aware of: Depstar and Juxt.Pack. For clj
and tools.deps.alpha
questions, you might want to join #tools-deps