This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2019-03-29
Channels
- # announcements (9)
- # aws (1)
- # beginners (133)
- # boot (2)
- # calva (94)
- # cider (48)
- # cljdoc (7)
- # cljsrn (22)
- # clojure (128)
- # clojure-europe (22)
- # clojure-finland (7)
- # clojure-greece (6)
- # clojure-losangeles (3)
- # clojure-nl (81)
- # clojure-spec (30)
- # clojure-uk (60)
- # clojure-ukraine (1)
- # clojurescript (45)
- # core-async (26)
- # cursive (18)
- # datomic (12)
- # defnpodcast (1)
- # duct (4)
- # editors (4)
- # emacs (6)
- # fulcro (37)
- # graphql (4)
- # jobs (2)
- # jobs-rus (1)
- # juxt (7)
- # kaocha (2)
- # leiningen (1)
- # nrepl (22)
- # off-topic (2)
- # re-frame (16)
- # reagent (8)
- # reitit (22)
- # ring-swagger (5)
- # shadow-cljs (81)
- # tools-deps (4)
Does the new nREPL actually require Java 8 for anything? I didn’t realise it had that dependency, and have started receiving issues from users who are using JDK7.
the change points here: https://github.com/nrepl/nREPL/issues/26
@dpsutton Thanks! Since the version in Cursive is only used when Cursive starts its own REPL, perhaps I’ll fork a version compiled against Java 6. But in general, it seems like it would be good to support older versions if newer ones are not required for anything.
from the ticket it doesn't look like raising the bar was intended unintended. I guess @bozhidar took 8 to be the current java version rather than the current bytecode version?
But Cursive is used a lot in enterprise environments, where upgrading is often not a choice.
No, I released it in the latest stable release, I hadn’t realised that it had a Java 8 dep.
Well, when users start a REPL via lein or deps, you get whatever they use, which is probably 90% of the REPL use. But some users start a REPL in a project not managed by one of those two (e.g. Maven, Gradle, manual project setup or some other means), and then Cursive injects nREPL to start the server.