This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
- # admin-announcements (1)
- # boot (24)
- # cider (8)
- # cljsjs (1)
- # cljsrn (5)
- # clojure (22)
- # clojure-greece (1)
- # clojure-italy (3)
- # clojure-russia (218)
- # clojure-spec (33)
- # clojurescript (51)
- # core-async (6)
- # cursive (1)
- # datomic (13)
- # defnpodcast (2)
- # funcool (2)
- # lein-figwheel (21)
- # onyx (41)
- # proto-repl (4)
- # protorepl (5)
- # reagent (4)
boot-new template can create any structure it wants: it's "just code".
As for the template names,
lein new have to use a convention for discovering templates but it would be an interesting enhancement to be able to override that and allow you to specify a particular coordinate... Do you want to open a GitHub issue for that?
@flyboarder: Actually, looking at the code, you could have a template
com.mycompany.mytemplate/boot-template -- I don't see anything obvious that would prevent you using a fully qualified group ID.
@seancorfield: I don't have an issue with using the fully qualified name for now, thanks!
I think what I’ll do is allow a template argument with and without
/ — if there’s no
/, it’ll auto-append
/boot-template like it does now.
@seancorfield: That's what I was thinking, makes sense, what should the project name be in that case?
TL; DR: I think you can just ask Boot to fetch the library directly and as long as it contains a
boot.new.thing/thing function, you can then use
-t thing for the template.
@flyboarder: Also remember that
-t specifies the template name to use and
-n specifies the project name to generate — they are not related.
so are there any projects that makes use of boot for a full stack clojure & clojurescript web app?
Also, it now points mistakenly to a version of boot-cljs-devtools that is not on clojars yet
oh sweet, PSA:
[foo/bar "0.1.0" :exclusions [*/*]] totally works. no transitive deps brought in
I’m having problems as different temp dirs are being created so I can’t resolve relative paths e.g. to