Fork me on GitHub
#cursive
<
2022-01-03
>
greg12:01:32

I tried to use "Clojure Application" configuration to run my custom namespaces that kicks off my repl. I noticed that if I choose "Run with Deps" I got:

class java.lang.Character cannot be cast to class java.lang.String (java.lang.Character and java.lang.String are in module java.base of loader 'bootstrap')
while when I choose "Run with IntelliJ proejct classpath" it starts ok (but complains later because the given namespace does not exist in the classpath because it is added only in specific deps alias - I guess this part is normal).

cfleming22:01:29

There’s an issue for this, I’ll look at it for the next EAP: https://github.com/cursive-ide/cursive/issues/2617

👍 1
genekim19:01:13

Just curious: how often do y’all update IntelliJ? I think I had one bad experience 2 or 3 years ago, and so now I update maybe once per year. (I just learned you can upgrade Cursive independent of IntelliJ upgrades! Duh.)

AJ Jaro15:01:09

I regularly update IntelliJ and Cursive; no issues here…for now. 😉

imre19:01:19

You learn something new every day

R.A. Porter19:01:31

I had a bad experience once, but the most I've done is stopped using EAPs. I "survived" the OSX update that nuked Java (by "survived", I mean I moved to a PC for several years), so my threshold is a bit higher. 😄

imre19:01:54

I am on the EAP channel of both IJ and Cursive. For IJ I usually upgrade to builds that my must-have plugins support unless I see problems posted in this channel. For Cursive I usually upgrade at the first opportunity after a new build comes out

Jeff Evans21:01:57

is it possible to disable (ideally temporarily) the Aviso exception printer when running a test? in essence, I’m running into this:

cfleming21:01:59

I don’t think there is, unfortunately. The way this works in Cursive is that when you print an exception, it checks to see if the namespace is loaded, and uses it if so. Perhaps you could just unload the Aviso namespace in tests?