Fork me on GitHub
#cursive
<
2019-10-09
>
chris_18:10:14

Hey, could I ask for some troubleshooting help? Has anyone else been having this issue? ###### PROBLEM: Error reading project.clj: Unable to resolve var: clojure.instant/thread-local-utc-date-format in this context Cursive version: 1.9.0-eap4-2019.2 Intellij version: 2019.2.3 (Community Edition) Lein version: Leiningen 2.9.1 on Java 1.8.0_102 Java HotSpot(TM) 64-Bit Server VM

Error reading /Users/concerto/cs/landschaften/project.clj
Syntax error compiling var at (fipp/ednize.clj:71:13).
Unable to resolve var: clojure.instant/thread-local-utc-date-format in this context
fipp is not a direct dependency but per lein deps :tree is present as a dep even for newly created lein projects. That specific error has been discussed several places, e.g. here [Cannot load fipp in Java 9 using bootclasspath](https://github.com/brandonbloom/fipp/issues/60), but not in connection to Intellij or Cursive. I’m able to lein run and lein repl (outside of Intellij) successfully. So I suspect the issue is Intellij and/or Cursive. I noticed this issue after upgrading to Intellij 2019. I did not change any dependencies or settings in my project.clj between then and the error. STEPS TO REPRODUCE: Create a new Lein project: $ lein new app testapp Then import to Intellij following Cursive docs instructions ([Cursive: Working with Leiningen](https://cursive-ide.com/userguide/leiningen.html)) e.g. File -> New -> Project From Existing Sources … etc. Wait until Intellij event log throws the error.

cfleming23:10:27

I’ll investigate this and follow up over on the issue.

❤️ 4
👍 4
😎 4
💖 4
tony.kay21:10:54

I’m no longer seeing auto-import of :local/root when I change deps.edn…is that an intentional change?

tony.kay21:10:08

I seem to be able to manually add it via the deps tab

cfleming23:10:26

@tony.kay Do you mean that when you modify a deps.edn to add a new :local/root dep, you don’t see that module added automatically?

tony.kay02:10:53

Yes. I have to press + in the Clj deps tab.

tony.kay02:10:10

I just upgraded to 2019.2 and latest EAP…which “upgraded” the project. Could be that.

Alex Miller (Clojure team)23:10:09

there is a known issue that changes in a local dep do not make the cache stale

Alex Miller (Clojure team)23:10:20

so you need to force a classpath recalculation in that case

cfleming23:10:32

I don’t think that’s the issue, Cursive doesn’t use any of the classpath cache stuff. I added an option when importing deps projects to transitively walk :local/root deps, but I don’t think that logic is present when syncing an existing project. I’ll add that.