I'm writing a blog post on updating to Java 9, does anyone have any feedback on it? Things I missed? https://deploy-preview-11--deps.netlify.com/blog/upgrading-clojure-projects-to-use-java-9/

@danielcompton that link doesn’t work for me

@alexmiller hmm, https://deploy-preview-11--deps.netlify.com/blog/how-to-upgrade-your-clojure-projects-to-use-java-9/

ah I updated the (not so) permalink, my bad

Just published cause I'm about to go to bed, but feedback still welcome https://www.deps.co/blog/how-to-upgrade-your-clojure-projects-to-use-java-9/

Hello, I have a question on how boot use Java classpath. I want to develop a web app that combines danielsz/system and weavejester/environ

;; dev/.boot-env
{:http-port "3000"}

;; project/systems.clj
(defsystem webserver
  [:web (new-web-server (env :http-port))])

;; build.boot
(merge-env! {:resource-paths #{"res"}})

(deftask with-dev "" []
  (merge-env! :resource-paths #{"dev/res"})
  identity)

(deftask run "" []
  (comp (with-dev) (comment start system)))

;; => error .boot-env not in classpath

I create a component system from environment variables via environ

In development mode, I store these variables in dev/res/.boot-env. I want to include this file in the classpath during development only.

thus, I created two boot tasks: with-dev to include dev/res in the resource paths and run to execute the system (a web server)

It works when I put .boot-env in res (the common resource paths), but not when the file is in dev/res

my understanding is that the classpath is loaded once build.boot is read, and that it cannot be changed by other tasks

@fmind boot's classpath can be changed dynamically. It can be changed by other tasks.

so do you know why I have this issue ?

should I change something else than resource-paths ?

the thing is: it works when I put the file in the top level merge-env!, but not the task level merge-env!

@fmind tasks need to return a function, You probably want to use with-pass-thru

https://github.com/boot-clj/boot/blob/master/doc/boot.core.md#with-pass-thru

(deftask x
  …
  (with-pass-thru _
    (merge-env! …)))

@dominicm I forgot the line in my copy paste, this is what I have:

(deftask with-dev "" []
  (merge-env! :resource-paths #{"dev/res"})
  identity))

@fmind that looks correct. Why do you think it's not working?

Try doing boot with-dev repl and then do ( ".boot.env")

I tried, and it gives me nil

@fmind is this open source? Can you share so I can try myself? Otherwise I will create a repo showing how I think this should work.

@dominicm well ... I tried to create a single repo to demonstrate the issue, and it works

i may have some strange interaction in my boot process

I'll have a look when I'm home. Thanks for the help.

No problem.

[boot-tools-deps "0.1.4"] released: depends on latest tools.deps.alpha and system defaults from brew-install; fixes how -r and -c options work (in light of discussion above about -Srepro); adds a -A option as a synonym for -R and -C both specifying the same alias for resolving and classpath updates.

@seancorfield hey! From your experience working with tools.deps — how hard would it be to say “here’s a deps.edn; go make me a pod with it”? I assume that should be relatively straightforward?

@martinklepsch Should be straightforward. Probably something I could refactor the code in boot-tools-deps to expose easily...?

If I refactored the main load-deps function out to return the three things it does here https://github.com/seancorfield/boot-tools-deps/blob/master/src/boot_tools_deps/core.clj#L81-L94 then you could just call that function from code that wanted to set up a pod I think?

Can you open an issue with what you'd like to see there?

@martinklepsch that's a nice nice idea...especially if the files comes from the fileset and therefore can be rewritten

in particular for pods in dependencies...`boot-cljs` could have a deps.edn that it marks with metadata :adzerk.boot-cljs and that it reads deps from. If other tasks want add stuff to the pod classpath they can rewrite the file

(brainstorming here)