@flyboarder: A boot-new template can create any structure it wants: it's "just code".

As for the template names, boot-new and 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!

Saw the new issue. Thanks @flyboarder !

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?

There’s actually another wrinkle — just documenting it in the ticket.

See my latest comment on the ticket.

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.

@seancorfield: just saw the ticket, thanks!!

@flyboarder: thanks

so are there any projects that makes use of boot for a full stack clojure & clojurescript web app?

Hoplon?

@renlore lots hoplon/javelin/castra is one way to do that

@renlore my lambone has the bare setup you need, but I would not recommend it if you are just.starting out https://github.com/Lambda-X/lambone

Also, it now points mistakenly to a version of boot-cljs-devtools that is not on clojars yet

(I am nudging the maintainer as we speak :))

oh sweet, PSA: [foo/bar "0.1.0" :exclusions [*/*]] totally works. no transitive deps brought in

how should relative paths be handled in Boot pipelines?

I’m having problems as different temp dirs are being created so I can’t resolve relative paths e.g. to node_modules

nice @alandipert that will make several of my deps files a lot cleaner...

I have a couple of libraries that currently have a loooonnnngg list of exclusions.