This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2021-07-19
Channels
- # announcements (1)
- # babashka (26)
- # beginners (42)
- # calva (3)
- # cider (5)
- # cljs-dev (7)
- # cljsjs (1)
- # cljsrn (13)
- # clojure (95)
- # clojure-europe (12)
- # clojure-germany (3)
- # clojure-italy (12)
- # clojure-nl (1)
- # clojure-spec (16)
- # clojure-uk (25)
- # clojurescript (13)
- # clojureverse-ops (5)
- # community-development (1)
- # conjure (8)
- # cryogen (3)
- # datomic (5)
- # deps-new (7)
- # exercism (1)
- # fulcro (34)
- # honeysql (9)
- # hyperfiddle (3)
- # instaparse (2)
- # introduce-yourself (2)
- # jobs (6)
- # kaocha (1)
- # lambdaisland (1)
- # lsp (47)
- # malli (3)
- # membrane (38)
- # off-topic (9)
- # polylith (36)
- # reitit (7)
- # releases (1)
- # remote-jobs (2)
- # shadow-cljs (11)
- # spacemacs (7)
- # sql (7)
- # tools-deps (19)
Is there a way to force clj-new
to always download the latest version of my template?
@rafaeldelboni By default, it will use RELEASE
which is the latest stable version, but the "Maven" libraries under the only check for updates once a day, I believe.
That should be the case them, I made two releases today (bug fixes hehe) and the second one wasn't showing up.
You can tell clj-new
which version to use for a template -- see the docs for the option -- and you can also tell it to use SNAPSHOT builds but, again, I think the underlying libraries only check once a day for a new snapshot version.
If you are developing a template, you can always test it by either running clj-new
directly in the template project or by running it in a clean directory with a "local" filepath for your template repo -- see the docs for the syntax for that.
clojure -X:new :template '"/path/to/clj-template::new-app"' :name project-name :args '[arg1 arg2 arg3 ...]'