Someone complained about it recently and I suggested ignore-classpath-directories, if it's not working, feel free to create a issue with detailed repro project

Mine also went to target after calling clojure -T:build

I don't think clojure-lsp should add that to the classpath automatically. I think it might have happened because I also have project.clj in that project, but even then

Yeah, I think the issue is, the classpath contains the target folder so clojure-lsp consider it as a source-path

I don't know a way to know that is not a source-path

This is my config:

{:ignore-classpath-directories ["target"]}

I think it's a good default to never put target on the classpath btw, I've never seen a Clojure project in which it was a source directory. But this config doesn't work

oh, I thought that setting was meant to be a boolean?

oh that's even more strange, since src is also on the classpath, why would I want to ignore that one

could you paste your classpath here please? it's printed when clojure-lsp is starting on server logs

2022-06-09T15:45:03.903Z  INFO [clojure-lsp.db:70] - [DB] Reading transit analysis cache from /Users/borkdude/dev/cli/.lsp/.cache/db.transit.json db took 185ms
2022-06-09T15:45:03.936Z  INFO [clojure-lsp.crawler:160] - [Startup] Using cached db for project root /Users/borkdude/dev/cli
2022-06-09T15:45:03.938Z  INFO [clojure-lsp.source-paths:209] - [Startup] Using source-paths from classpath: ["/Users/borkdude/dev/cli/dev-resources" "/Users/borkdude/dev/cli/.build" "/Users/borkdude/dev/cli/target/classes" "/Users/borkdude/dev/cli/resources" "/Users/borkdude/dev/cli/src" "/Users/borkdude/dev/cli/src" "/Users/borkdude/dev/cli/test" "/Users/borkdude/dev/cli/test"]

Alright, before that log, it should have a classpath string and the command clojure-lsp used right? probably /Users/borkdude/dev/cli/target/classes is on the classpath returned by lein/clojure

so the target is on the classpath, that's the problem

we would need to know some way to ignore that

I don't see anything before that

but ignore-classpath-dirs doesn't ignore it

the only thing that works is actually deleting the target dir

I suspect ignore-classpath-dirs is broken since we started using source-paths from classpath

and I don't know a proper way to fix it since the target comes from the classpath

could you clojure -Spath or lein classpath ?

I think it's safe to always ignore target

I don't even want to use the classpath from lein btw, I just added a project.clj because I needed to deploy

Not sure it's safe to ignore the source-path just because it includes target string

ok, but then maybe ignore-classpath-dirs should be configurable as a regex or so?

gotta go

yeah, maybe

I'll take a look soon, and try to make :ignore-classpath-directories-regex ["target"] possible, and probably with that value as default

awesome! now to clojure meetup in Berlin :)

@U06M4ST0F do you have a simple project where I can test it while implementing it?

I think my case is a bit more complicated - I have resources in my path so I don't think ignore-classpath-directories would work for me

I'm going to try and work around by setting :source-paths

but what you have inside resources? clojure code similar to target dir?

the clojurescript compiler is dumping cljs files into my resources/public/js/compiled

if so, the suggested fix would work for you too right if you have something like :ignore-classpath-directories-regex [".*resources.*"]

alright, so something like :ignore-classpath-directories-regex ["resources/public/js/compiled.*" "target.*"] seems to make sense as a default too

If you could provide a sample repro, it'd help a lot to fix the issue on my side

OK, I'll try to put something together soon

Thanks for looking into this 🙂

Ah, I just noticed this was fixed recently. Thank you so much! (and apologies for not getting around to setting up the repro)

I did run into this again today :( let's hope this was just a one time quirk

yeah, no, it wasn't fixed, I can reproduce the same problem again still

https://github.com/clojure-lsp/clojure-lsp/commit/69a9a5c42fc852d46ecbd17aab28a9e6e9f5c055 didn't do the trick eh?

nope

and I was editing a file in target for half an hour until I noticed I was editing the wrong file :(

My problem with resources seems to have gone away

hmmm, with lsp-clojure-server-info it seems emacs is picking up an older version

sorry, then that's my bad

@UKFSJSM38 Suggestion: add to the lsp-clojure-server-info which binary is currently being used? does it pick the one from the path automatically?

or does lsp-mode have a way to show this?

Problem seems to be gone now, now that I've fixed the setting

Hum, not sure if from server side it's possible to know it's path, if not, we could maybe add it from lsp-mode, it'd just be a little trick to edit the edn on elisp

ok no problem, I got it fixed now