This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2023-03-29
Channels
- # admin-announcements (1)
- # announcements (20)
- # babashka (43)
- # beginners (134)
- # calva (2)
- # clerk (7)
- # cljdoc (9)
- # clojars (8)
- # clojure (91)
- # clojure-europe (21)
- # clojure-nl (1)
- # clojure-norway (13)
- # clojure-uk (1)
- # clojurescript (5)
- # datahike (3)
- # docker (2)
- # emacs (6)
- # fulcro (7)
- # graphql (9)
- # honeysql (24)
- # improve-getting-started (5)
- # introduce-yourself (1)
- # lambdaisland (1)
- # luminus (3)
- # malli (3)
- # nbb (19)
- # off-topic (22)
- # pathom (1)
- # portal (3)
- # practicalli (1)
- # rdf (26)
- # reagent (29)
- # reitit (9)
- # shadow-cljs (15)
- # spacemacs (3)
- # sql (4)
- # tools-build (30)
- # xtdb (41)
Lein uberjar
produces two jar files, one with the full-name of the application with the version number and another with just app.jar, the later one is larger in terms of size, which should one use ideally and do they represent the back and front end of the application respectively?
It looks like nobody answered this. The larger one is the überjar, which contains all of the dependencies. This is what you need to deploy. The smaller one is the result of compiling just your application, and would be suitable for use as a library in a context where Maven (or Leiningen or some other Maven-based tool) is managing the dependencies.
…say when you did like to deploy to Elastic Bean Stack