@seancorfield if I wanted it the other way round, so I could aot, how would I do that?

What is the intention of source-paths vs resource-paths again?

source paths get processed, and don't go into target. resource paths may be processed, and do end up in target.

https://github.com/boot-clj/boot/wiki/Filesets#fileset-components

thanks

I'm struggling to pass data in the boot pipeline, I've tried setting atom in let binding and reset! it to be read in the next task sequence, but the atom isn't mutated when its dereferenced, and also do a let binding

(deftask x []
  (comp
     (task1)
     (with-pass-thru _ 
        (let [data-i-need (fn)]
           (comp (task2 data-i-need)
                (task3 data-i-need)))
    (task4)))

so what I'd love to be able to do would be something like this

(deftask a []
  (with-pass-thru x
    (assoc x :data "wow")))

(deftask b []
  (comp (a)
        (with-pass-thru x
          (prn (get x :data)))))

that's an intriguing idea -- i wonder if there is some place in the fileset where we can hang arbitrary data

i don't know too much about what kind of object a fileset is

Hello, boot friends. I’m writing a boot library for internal company use which provides tasks for deploying things to our infrastructure. That part’s going nicely, so now I’m looking to see how I might also use it to inject our internal maven wagon and repositories into a boot project. Absent such a library, a boot file would would contain something like (set-env! :repositories #(concat % [["releases" {:url ""}]]) :wagons '[[sparkfund/aws-cli-wagon "1.0.4"]]). How, if at all, would it be recommended for boot libraries to set such environment values in a boot file that requires them? Obvious options would seem to include: at ns load time or by providing a fn to call.

donaldball one thing i considered but never did was 2 set-env! calls. i think it's competitive with 'managed dependencies' maven concept

i.e. one set-env! adds a dependency that contains clj code for loading more dependencies

oh, and i think we now support managed dependencies

i think most of this is applicable (we have the :managed-dependencies set-env! key) http://127.0.0.1:8080/

err, https://github.com/technomancy/leiningen/blob/master/doc/MANAGED_DEPS.md

Oh that’s actually looks useful. I use a task like this https://github.com/nha/boot-deps/blob/master/src/nha/boot_deps.clj#L159 when I add a new dependency, which usually adds a lot of :exclusions to it, and then I still have to sometimes pin a specific dependency version, even if I don’t use it directly.

@juhoteperi Interesting. I'm always a little nervous of using metadata because so many operations cause it to "evaporate"...

Hamming my head against a wall. I try for hours now to create a task to pack html and images in gui/dist into resources/public. Most boot file commands relate to files. Any idea how to do this with directories?

@usenet the sift task has a move/rename option but it depends a bit on whether you want to copy your files to your actual resources/public directory or the target/public directory that is eventually emitted when you use the target task

Hello all, how do you use local jar from local maven like I use in lein-localrepo in boot?