Fork me on GitHub

@cfleming How's Cursive support for deps.edn these days?


Encouraging Boot users to migrate to deps.edn and use boot-tools-deps for other stuff on top seems like a potentially viable path for Cursive (given Boot's completely dynamic approach to build dependencies otherwise).


Is anyone working on reducing the variance between boot-tools-deps and the clojure deps tools?


@seancorfield Still absent, but I’m planning to add that first for exactly that reason. It won’t make arbitrary boot projects more usable in Cursive, but it will at least give boot users a way to make their projects more Cursive-friendly.


@donaldball As the maintainer of boot-tools-deps I'd be interested to here what variance you'd like reduced?


@donaldball bumping this in case you didn't see it last night...


Oh, hah, sorry! I’d been laboring under the misimpression that boot-tools-deps didn’t support git dependencies, though I don’t see that called out in fact.


From the Changes section of the README: > 0.2.0 -- 01/28/2018 -- Update to use the most recent tools.deps.alpha release; directly update the Boot classpath (which means Git and Local dependencies are now supported!); run tools.deps inside a Boot pod; no longer update Boot's :dependencies by default.


\o/ I withdraw my foolish query


Seriously tho', if anything bothers you about boot-tools-deps, bring it up with me or open a GitHub issue -- I want it to be the best Boot + deps tooling it possibly can be.


@cfleming Good to know. Thanks Colin!


@donaldball boot-tools-deps uses tools.deps.alpha directly to produce the classpath so anything you do purely based on the classpath ought to have zero variance. The difficulties arise when you need to shoehorn that into Boot's model of :resource-paths, :source-paths, and :dependencies -- which is what the -B and -Q options are for...


@seancorfield How does boot-tools-deps work with git deps?


@seancorfield Actually, thinking about it, never mind - from Cursive’s point of view these projects would just be deps projects, and I’ll integrate with that directly.


I am trying to connect to a clojure repl running in vagrant from host machine. I am getting this error:

SocketException The transport's socket appears to have lost its connection to the nREPL server (transport.clj:95) (transport.clj:95) (transport.clj:42)
        clojure.core/binding-conveyor-fn/fn--5476 (core.clj:2022) (:-1)
        java.util.concurrent.ThreadPoolExecutor.runWorker (:-1)
        java.util.concurrent.ThreadPoolExecutor$ (:-1) (:-1)
The boot task I am using is
(deftask dev
  "Run a restartable system in the Repl"
   (environ :env {:http-port "9000"})
   (watch :verbose true)
   (system :sys #'base-system :auto true :files ["handler.clj" "html.clj"
                                                 "pipeline.clj" "steps.clj"])
   (repl :server true
         :host ""
         :port 62000)))
I have tried with the host key and w/o to no luck. I have forwarded the relevant ports in the vagrantfile "forwarded_port", guest: 9000, host: 9000 "forwarded_port", guest: 62000, host: 62000
I am able to see the server at port 9000 but not able to connect to the repl.


I can see that nrepl is successfully started

Starting #'
nREPL server started on port 62000 on host - 
Elapsed time: 2.871 sec


What are the things that I can try to resolve this ?


@cfleming boot-tools-deps defers to tools.deps.alpha to build the classpath -- complete with downloading/unpacking/analyzing any git deps, or local deps, along with any other deps.edn stuff -- and it then uses that classpath for subsequent operations in the task pipeline. Some Boot tasks only work from :resource-paths, :source-paths, and/or :dependencies, so boot-tools-deps provides options to overwrite all of those from what it finds on the classpath (`-B`) or merge the classpath into those (`-Q`). It puts :paths from deps on :resource-paths, :extra-paths from deps on :source-paths, all JARs into :dependencies (based on the library list that deps figures out), and any folders from the deps (the local and git deps) into :source-paths. It's not a perfectly 1:1 mapping from deps to Boot but it's close enough (via overwrite or merge) to work for nearly all tasks.


@shakdwipeea Perhaps something else is trying to use port 62000 -- maybe try a different port, like 50505 or even 5555?


@seancorfield tried that, it gives back the same error.


One thing I noticed was, even if in my task I specify the host to be "", the nREPL server is still started on <nrepl://<port>> . Is this expected ?


Solved it. The trick was to set the :bind key to "" and not the host.

(repl :server true
         :bind ""
         :port 50505)
This works.


Ah, I hadn't even noticed that. Sorry. Glad you got it working!

👍 4