I keep running into this weird bug in Cursive - increasing the version number of a dependency does not make Cursive aware of it. It can't see the newer dependency and will insist on using the old one.

What's worse is that when I finally do manage to convince Cursive to use the newer version (through manual editing of the project's .iml file) it will still start any REPL sessions with the old dependency.

This is happening on the latest IDEA 14.1 with the latest Cursive plugin.

@sgerguri: You need to refresh the dependencies after editing your project file.

You can do it in the leiningen toolwindow (refresh button) or by executing the “Refresh Leiningen Projects” action from Cmd-Shift-A

That did not help. 😕

Editor is picking the new version up just fine, but REPL is still being started with the old version.

So if you look at the project structure view, you see the new version added to the module, right?

Cmd-; on mac, at least

Look at the module view, then check the dependencies of your module.

Yes - I see it there, in the latest version.

Ok. What sort of REPL are you running?

Interestingly, the Project view lists both versions in the 'External Libraries' tree.

Do you have multiple modules in your project?

nREPL with Leiningen, with the correct project

Ok, and in the classpath, it’s definitely picking up the wrong version? You can see that by unfolding the first line in the REPL window.

Yes I do, and that's another bug - if I remove them they'll be added eventually automatically when I restart the IDE.

Although to be fair that sounds more like a bug in IDEA rather than the plugin itself.

That’s not a bug

You’re talking about manually modifying the module file, right?

It's picking up the right version, which is strange.

That doesn’t sound strange

But it's clearly complaining about an import in a ns that uses a function from it.]

And the function is there.

Or maybe I'm just dumb.

What does the import look like?

require with multiple refers

It's complaining about one of those.

I can click through it to its definition, so it should be correct, no typo etc.

Can you send a screenshot of the require?

Re. module file - either through the Project view, or through project settings.

If you modify the module file, those changes will be overwritten the next time the Lein project is synced (opening your project, manually refreshing etc)

The Maven integration works the same way.

The idea is your module should reflect what is in the project.clj, and Cursive will make it like that every time.

^ That's the require line. Everything except delete-item! works.

Although like I said, delete-item! can be clicked through to its definition from here. And it's using the download deps for that.

And if you click to delete-item!, you can … right. What does its definition look like?

Re. modules - I was referring to other Clojure projects that I have merely added as 'new modules from existing sources'.

I may be missing sth but I can't see anything in project.clj that would refer to them.

So you add them as modules, and later they disappear?

I add them as modules, but cannot remove them permanently - they'll be added back the next time I restart the IDE.

Are they leiningen modules?

Yes, all of them

^^ That's the clicked-through fn that I'm referring to.

It's on a yellow tab, so that's a dependency.

Ok, then you have to delete them from the leiningen toolwindow. Select the project, and remove it from there. It’ll ask if you want to remove the associated module, say “yes"

I’m not sure if I can catch the deletion of a module in IntelliJ and remove the lein part automatically.

Ah, that seems to have worked. It's a bit quirky, since normally I interact with the Project view so I'd like to remove it from there, but as long as there's a reliable way of doing it it's ok.

That hasn't changed anything about delete-item! though.

No, that’s weird. So what do you see - Cursive says it can’t be resolved?

It gives me CompilerException in the REPL.

When I load the ns, that is.

Oh.

Does it work using lein repl?

Cursive should be doing basically exactly the same thing.

i.e. it delegates all that to lein.

It doesn't. Glad to see the problem is elsewhere (likely between the keyboard and the chair).

Phew

Well, sorry about the false alarm!

No worries, glad it’s working. Or at least, it’s not working in a consistent way.

yeah