Closed bbatsov closed 6 years ago
It sounds like a good approach for me.
I like the idea of adding a new nrepl
task :+1:
@alandipert I'm not sure if that makes sense any more, as pretty much all of the essential middleware got updated to support nREPL 0.4 while this and #703 stayed open. Seems to me at this point it would just be simpler to directly switch to 0.4 (and that's also what lein did already - it switch to nREPL 0.4 in master
).
If you insist on a boot nrepl
we can make this happen, though.
That's basically a follow up of nrepl/nREPL#1 and was also discussed in nrepl/nREPL#4.
TL;DR; - In verions 0.4 of the "new" nREPL the namespaces will be changed from
clojure.tools.nrepl.*
tonrepl.*
.As this is a different artifact technically speaking(
nrepl/nrepl
instead ofclojure.tools/nrepl
) I think the best migration path for Boot would be to just start depending on both projects and have two tasks for the two nREPLs until we can drop the old version (e.g.boot repl
andboot nrepl
). The second task can just start a headless server until reply adds support fornrepl/nrepl
.How does this sound?