Cursive 1.8.0-eap4

302 views
Skip to first unread message

Cursive

unread,
Jul 31, 2018, 11:05:33 PM7/31/18
to cur...@googlegroups.com

Hi everyone,

Cursive 1.8.0-eap4 is out. It contains various fixes and improvements to the deps support. In particular, you can now use tools.deps directly rather than using the CLI tools, which means that Windows users can now manage their projects with deps. This has some caveats, in particular the system deps.edn is bundled with Cursive, so it will always use the current version as of the time of this writing. There is some consideration being given to bundling that into the tools.deps jar rather than installing it via the CLI tools, if that happens this limitation will go away.

The configuration of this is currently a little clunky. You can configure it either at Settings->Build, Execution, Deployment->Build Tools->Clojure Deps or in the global settings section when setting up a new project. Select “Use tools.deps directly”, then press the “Refresh” button to get the list of available versions. Select the version you want to use (by default the latest is selected) and then press “Download” to fetch the artifacts from Maven. You should then be good to go. If required, you can also customise the path to your user deps.edn file if you want to do so.

Note that this doesn’t require or use WSL at all, and in fact it can’t - IntelliJ lives entirely in Windows land and can only read files from WSL. If you’ve been using deps under WSL you’ll probably have to copy your user deps.edn somewhere accessible, or point Cursive to it as described above. I don’t use Windows myself, so any feedback about how well all this works is very welcome.

This EAP also fixes some annoying issues - one error while indexing, a StackOverflowError when editing some CLJC files, and a problem which prevented custom repo certificates from being used under lein.

Here are the issues:

Allow using tools.deps directly #2019
IndexNotReady exception on project open #1996
com.intellij.openapi.project.IndexNotReadyException: Please change caller accord #1985
Having trouble with finding relative certificates from project.clj #1156
StackOverflowError in CLJS code #929

Cheers,
Colin

marco.molte...@gmail.com

unread,
Aug 6, 2018, 5:13:21 PM8/6/18
to Cursive
Hello Colin,

the https://cursive-ide.com/ documentation doesn't mention tools.deps. In my opinion it would make sense to have a page dedicated to it, to make Cursive even more appealing :-)

Colin Fleming

unread,
Aug 6, 2018, 10:54:23 PM8/6/18
to cur...@googlegroups.com
Yes, definitely. However that support is only in EAP at the moment, so I'll document it properly when it's finally released.


On Mon, Aug 6, 2018, at 2:13 PM, marco.molte...@gmail.com wrote:
Hello Colin,

the https://cursive-ide.com/ documentation doesn't mention tools.deps. In my opinion it would make sense to have a page dedicated to it, to make Cursive even more appealing :-)


--
You received this message because you are subscribed to the Google Groups "Cursive" group.
To unsubscribe from this group and stop receiving emails from it, send an email to cursive+u...@googlegroups.com.
To post to this group, send email to cur...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

dan young

unread,
Aug 8, 2018, 11:37:21 AM8/8/18
to cur...@googlegroups.com
Is there any documentation/cliff notes one could reference for peeps using the EAP and would like to try out the deps.edn integration/usage?  


Regards,
Dano




Colin Fleming

unread,
Aug 8, 2018, 7:58:01 PM8/8/18
to cur...@googlegroups.com
Not yet, but here are the basics. These should be familiar to anyone who has used the other IntelliJ build integrations (lein, maven etc).

  • To import an existing project, you just need to import the root project, not any deps referenced via :local/root - they will be discovered transitively. For a simple single-root project you can use File->Open..., and then select either the deps.edn file or its containing directory.
  • To import, you can also use File->New->Project from Existing Sources... If you select deps.edn it will open automatically, otherwise select "Import project from external model"->"Deps"
  • To create a new project, use File->New Project...->Clojure->Deps, check "Use auto-import", although I suspect that's not working at the moment. Next, give your project a name, and you'll have a new project.
  • Once you have a project, you can see the overview using View->Tool Windows->Deps. If you add new deps to your deps.edn, currently you'll probably have to hit the refresh button there for those to take effect.
  • If you need to use aliases to sync your project correctly for development, in the toolwindow open your project tree element, then Aliases, check the aliases you want to be synced with your project and then refresh again.

Any questions, let me know!

Colin Fleming

unread,
Aug 8, 2018, 8:16:01 PM8/8/18
to cur...@googlegroups.com
Oh, and I forgot to mention - there is an annoying bug where depending on how you create your project, the Deps toolwindow will not be created correctly. If this is the case for you, just close and re-open the project.

dan young

unread,
Aug 16, 2018, 7:12:16 PM8/16/18
to cur...@googlegroups.com
Works great so far w/ my clojurescript project.  Thanx!

Regards,

Dano

Reply all
Reply to author
Forward
0 new messages