boot

:boot-clj: https://boot-clj.github.io/ — build tooling for Clojure. Dev chat in #boot-dev
isker 2018-11-11T22:01:27.056700Z

https://github.com/boot-clj/boot-figreload#usage can anyone explain why i also need boot-http for this to work?

2018-11-11T22:37:30.057200Z

Where does boot look for Java ?

2018-11-11T22:37:56.057800Z

I'm on Windows. I have Java on my path, but boot thinks I don't, and sends me to the download link.

2018-11-11T22:56:22.058400Z

Okay, I figured it out. Boot.exe uses launch4j which finds Java based on registery keys, and not the environment variables. :face_with_open_mouth_vomiting:

2018-11-11T23:11:31.058600Z

Now I'm getting : unable to find valid certification path

2018-11-11T23:11:45.058800Z

Caused by: sun.security.provider.certpath.SunCertPathBuilderException

2018-11-11T23:12:14.059400Z

Maybe I should just abandon trying to get Clojure working on Windows 😿

2018-11-11T23:13:21.059600Z

Caused by: org.sonatype.aether.transfer.ArtifactTransferException: Could not transfer artifact boot:pod:pom:2.7.2 from/t o clojars (https://repo.clojars.org/): sun.security.validator.ValidatorException: PKIX path building failed: sun.securit

geoffs 2018-11-11T23:31:25.064700Z

Because tasks in boot are so easily composed, they tend to follow the unix philosophy of “do one thing well.” boot-figreload does live code reloading of clojurescript code, and boot-http serves static files and/or a ring application. They have nearly totally orthogonal purposes and can be used independently of each other.

geoffs 2018-11-11T23:33:47.068100Z

The real dependency of figreload is actually having an http server to get the first set of compiled js into the web browser, because figreload has some client side code that communicates via websocket with the boot task. boot-http is a convenient boot filesystem aware http server.

geoffs 2018-11-11T23:34:01.068600Z

Hope that helps :)