btw, few days ago I played around a bit with filesets of varying sizes: https://gist.github.com/martinklepsch/6291206cff000a0182a0, will put it in a repo soon, not sure how useful it is though

Gist is:

100 files: 200ms
1000 files: 2s
3000 files: 6s

Looks linear.

hey. Is there a way to make boot download all dependencies for a project?

... without actually performing boot dist (e.g.)

I tried boot show -e but it only download some jars, not all

@pesterhazy: it’s not as easy as in lein since dependencies are dynamic and can be modified by tasks but basically you can make a deps task that just looks like (deftask deps [])

more can be found here: https://github.com/boot-clj/boot/wiki/Boot-for-Leiningen-Users

@pesterhazy: the deps task will download everything that has been specified via set-env!/ merge-env!

will that also download cljs dependencies, e.g.?

if they’re specified

ok I'll try that

Boot/Lein etc. usually don’t care if it’s a cljs or a Clojure dependency. Only thing that might be relevant in that case is the maven scope.

@juhoteperi: gpg stuff looks great!

i was hesitant at first about the :gpg and :env conventions because they add magical names, but i think i'm warming to it

What’s the jvm option I need to set again when (pst *e) just returns a single line?

nvm, probably better asked in #C03S1KBA2

-XX:-OmitStackTraceInFastThrow

OK, I am having problems getting boot to update from maven recently built snapshots. The workflow is:

go into project A
lein deploy
go into project B
boot show -U

nothing gets updated.

now, if I do:

go into project A
lein deploy
go into project B
lein deps

Then I get updated project A

When leiningen deploys, it does update information in the local repo indicating that there is a more recent snapshot (maven-metadata-snapshots.xml). Leiningen must check this while boot currently does not. I can research this if there isn't a known solution.

@chrisn: that would be worth researching, but a workaround -- if you can use boot to build/deploy project A -- is boot checkout, see boot checkout -h for more info

another way is to add A's sources to B's resource-paths

the latter would let you dev as if they were the same project, more or less... while still deploying A separately

OK, more background. I just started using boot. I am trying to build an automated build system for multiple projects that are interdependent. They currently use leiningen for their build system. On the build server, I want to (in dependency order) do:

lein test && lein deploy

So using checkouts is not what I want because I would like the snapshost in maven for the rest of the team if they pass their respective tests.

And the docker image is for deploying to ec2.

I have literally all of this working except for updating dependencies.

which I guess lein install avoids.

i see. in this case, i would probably attempt to keep them all in the same boot project

but i don't have an example handy of doing that

it might be worth posting to discourse, see what people are doing in this area

@alandipert: does deps-cljs require lib files to be included?