This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2019-06-03
Channels
- # announcements (12)
- # beginners (44)
- # boot (27)
- # calva (73)
- # cider (1)
- # clj-kondo (9)
- # cljdoc (9)
- # cljs-dev (15)
- # cljsrn (6)
- # clojure (90)
- # clojure-dev (5)
- # clojure-europe (4)
- # clojure-ireland (3)
- # clojure-italy (22)
- # clojure-mexico (2)
- # clojure-nl (8)
- # clojure-uk (32)
- # clojurescript (12)
- # core-async (2)
- # cursive (16)
- # data-science (10)
- # datascript (3)
- # datomic (44)
- # emacs (17)
- # events (4)
- # graalvm (1)
- # hoplon (5)
- # jackdaw (17)
- # keechma (11)
- # nrepl (7)
- # off-topic (24)
- # re-frame (19)
- # reitit (4)
- # rewrite-clj (2)
- # robots (9)
- # shadow-cljs (20)
- # sql (12)
- # testing (4)
- # tools-deps (23)
- # vim (55)
Hello! I want to build a project that uses boot on Windows. boot.exe requires java 1.7.0 which is a really old version that I really don't want to install. Is there some other way to install/run boot on Windows?
@markus.gustavsson244 use Windows Subsystem for Linux and run boot as if it were on Ubuntu
just make sure you are using the latest build of Win10
(I have a task in a build pipeline that takes time because it downloads the dependencies, however they are already copied in /root/.m2
- but it may not be the place
@nha it’s almost always ~/.m2
unless you have changed it
Ah so is boot being run as root then?
That’s probably why it’s using that location
If you are in a container the deps will download every time, since when the container starts up again it has no deps
You would need to build a container after downloading the deps if you wanted to cache them
right but I have the deps on the host and I tried docker cp
on the container and setting the volumes
in docker-compose
@nha I’m not sure that will work, you would need a volume that mounts your host m2 to the root m2 in the container
I mean I’m sure it can work, the same way as replacing the working directory, I just don’t know what it would be off hand
Well I seem to be able to copy the files (I can docker exec -i my_container ls "/root/.m2"
etc) but it doesn’t seem to be the right place for boot
so I was thinking maybe it looks somewhere else and I wanted to check that - but I must have missed something
@nha it’s possible boot is using two places, but I don’t know without taking a look at your docker setup
I think before making a reproducible example I might just try and set BOOT_LOCAL_REPO
- see what happens
Yeah that’s the easiest way to see what’s going on, it might not matter tho, again depending on which container images you are using
here is the container - https://gist.github.com/nha/bdbde7768f0724b63d1fad9122b3b5c2