This is fixed in the next EAP, they now obey the Usages setting in that Settings dialog.

Thanks!

Here is the project I’m working on, and this issue exists in the main branch. https://github.com/jeff303/kc-repl

Every time I “Refresh Clojure Deps Projects” with Cursive, the main .clj source file I have under src is no longer under a source directory. If I add it manually, using the IntelliJ dialog, that works until the next time I need to refresh Deps again.

This is IntelliJ IDEA 2023.3.4 (Ultimate Edition) with Cursive 1.13.1-2023.3

Now, I am fully willing to accept/admit that my deps files for my project are screwed up, since I’m still learning the intricacies of handling multi-module setups. However, I’m 99% sure something this basic shouldn’t be happening. 😞

And in traditional rubber duck style debugging, this can be disregarded. My local IntelliJ state was all screwed up from some combination of 1) misusing/abusing deps, 2) upgrading major versions a few times, 3) planetary movements I nuked all .idea dirs, .iml files I could find in the entire tree, and started over from scratch, and all is good now. 😌

Actually, I stand corrected. It is still happening. Something to do with the multi-module setup, no doubt, as test somehow got associated with one of the submodules

Do you have your build alias ticked in the deps tool window by any chance? If yes, try without it

Not checked in either aliases or tools aliases

OK, yeah, it really doesn’t like that I’m bringing in the root project using the relative path, even though this is seemingly legal in deps: https://github.com/jeff303/kc-repl/blob/main/type-handlers/protobuf/deps.edn#L4 When I deselect the alias that brings these submodules in, then the problem stops happening.

Interestingly, if I just move that to be under the :build alias instead of the root :deps then the problem is fixed too (and no other ill effect, seemingly). So I’ll go with that for now.

I.e. this: https://github.com/jeff303/kc-repl/pull/19/files#diff-8035c851600b99baec44ab8c3c1273b2194b4e9b916a4248ed3b2b392d25dc07R14

I’ll take a look at this tomorrow

this happens to me whenever there's a problem resolving a dependency after refreshing deps

I can’t reproduce this with the latest version of your code. I have imported the project, and added the test-dependencies and type-handlers aliases. It all seems to sync correctly, and the src folder stays marked as src.

Sorry, I should have clarified the workaround I used did fix it

Your setup does create cyclic dependencies between modules, which is pretty funky.

Yeah... I'm not sure how to structure things differently

This is so that the sub-modules can access test code in the parent module, correct?

Not test code anymore. I already created a new submodule for the. Really just the main source code

This kind of thing is fairly common in Reactor (Maven) where you include subprojects which themselves depend on the parent

Hmm. I wonder if I could just move the main source to a new submodule too

Yeah, generally cyclic dependencies like that are a bad idea, they’ll often cause problems but it looks like both deps and IntelliJ are handling it ok.

I’d try to remove them if possible though.

It looks like your submodules mostly need the type handler bit. Could that be broken out into a sub-module?

Then the main module and the submodules could depend on that.

Excellent suggestion, thank you. And sorry for the noise