Fork me on GitHub

@hlship do you have a workaround for the “Everything cannot be resolved” issue?


Yes, unfortunately — downgrade your IntelliJ to 2018.3 and use the Cursive 1.8.2 EAP build.


Actually, the most recent Cursive should be fine, it’s the IntelliJ 2018.3 which is important.


Hi all, I’m evaluating Cursive, and I immediately run into an issue that I don’t understand. I have a deps.edn-based project that I imported in Cursive. I then try to create a (local) REPL run configuration (type: nrepl, how to run: tried both “run with IntellIJ class path” and “run with deps”). When I try to start that REPL, I get a little red balloon saying “Error running ‘REPL’: ‘10’ is bad configured”. I haven’t got the foggiest where that ‘10’ is coming from, and I don’t see any additional information. Any ideas?


@stefan.van.den.oord Yes, I’m sorry - that message is a bit impenetrable, it comes from IntelliJ. I’ll have to see if I can wrap it.


What it’s talking about is your Java SDK, which you can find under File-&gt;Project Structure-&gt;SDKs. Generally just deleting it and recreating it is the best way.


Ah yes, thanks @cfleming and @U0CKQ19AQ, the Java SDK was indeed the problem. I had recently reinstalled them using adoptopenjdk instead of from Oracle, and I forgot that I also needed to update IntellIJ for that. And I’ll also add clojure as suggested, thanks for catching that!


This is my deps.edn:

 {clj-http {:mvn/version "3.10.0"}
  org.clojure/data.json {:mvn/version "0.2.6"}
  commons-validator {:mvn/version "1.6"}
  expound {:mvn/version "0.7.2"}}

 {:run {:main-opts ["-m" "metrics-server.core"]}
  :test {:extra-paths ["test"]
         :extra-deps {lambdaisland/kaocha {:mvn/version "0.0-521"}}
         :main-opts ["-m" "kaocha.runner"]}}}


@stefan.van.den.oord I have some guesses around what I would try: 1. I would add an explicit dep on Clojure in the main deps. 2. I would also Look in “module settings” for the project (right click on the project name in the project sub-window …it’s near the bottom). Look through the modules and make sure there is a JDK selected, etc. 3. Make sure you have the clojure tools deps stuff installed from CLI…I think the normal deps support prefers to use that.


@cfleming I don’t want to cause noise in issues, but I have an idea that I wanted to share: I was thinking that library-based code analysis tools would be super-helpful if they could be somehow run in the context of Cursive and add warning/error markers to a problems list. For example, if got to a usable level how cool would it be to get “compiler error” kind of static proof spec checks (you’re pulling key :x from a map that cannot possibly contain it) for code as you program? I’m not suggesting you do the work to build the actual code-validation part, just a way for such libraries to integrate with Cursive so that the IDE experience could be awesome. Perhaps a way for code running in the REPL to call a function to add a report marker, which would make it possible (via the add REPL command/kb shortcuts) to have a key sequence that would check the current ns and add the marker. Would allow library authors to integrate with the IDE without you having to maintain anything but a “clear/set marker” API.


@U0CKQ19AQ Sorry, I missed replying to this the other day. Actually clj-kondo already does something like this, see:


My apologies for the lack of a build supporting the 2019.2 EAP yet, there have been a series of platform issues which have meant that I haven’t been able to release it. I’m hoping it’ll be resolved soon.