clojure-lsp finds the source-paths from the classpath, for deps.edn running this command by default:

clojure -A:dev:test -Spath

Didn't you mean :extra-paths instead of :paths ?

otherwise it will override indeed

I thought the same too

tried :extra-paths but then tried to remember why I used :paths

looked into tools.build guide https://clojure.org/guides/tools_build

> As mentioned above, running a tool with -T will create a classpath that does not include the project :paths and :deps. Using -T:build will use only the :paths and :deps from the :build alias.

so maybe there is a bit of a dilemma, that I don't know how clojure-lsp would know if an alias is a tools.build alias

Hum, I see

I wonder if there is any flag or command we should call clojure from clojure-lsp to workaround that

thanks for replying btw. wasn't sure if I'd make a issue to repo or just post slack message 🙂

was thinking that could :paths be merged, don't know if that would cause problems elsewhere though

yeah, that issue is that in the past clojure-lsp use to manually read the edn and handle all those things but it was pretty complicated to handle all edge cases which now are pretty well handled delegating to the classpath command, probably there is something we could do to avoid that changing the clojure command globally or customizing for your project, but I'm not sure where is the issue yet. What is your use case for clojure-lsp? editor? lint? dump?

I'm using Emacs

ah yes and now I see the override happens in clojure cli itself hmm

Right, so you are probably missing the source paths in the editor right? I think there is something you can do

could you check what source-paths show in lsp-clojure-server-info ?

I removed the alias that I used for tools.build in .lsp/config.edn and the :source-paths look correct now (thanks for the tip, used dump the get that same info)

so I guess I could configure :source-paths in .lsp/config.edn

yes, but usually I recommend use :source-aliases setting instead of manually setting :source-paths

yep

but not sure if will fit your case, since you just need the paths from :build sounds like it will work

clojure-lsp will build a command like:

clojure -A:build -Spath

yep, so a :paths in an alias would override top-level path and clojure-lsp doesn't itself have a change to do anything for the matter

hum, yeah

if there isn't a way to use clojure cli in a different way

you can still configure :source-paths setting for that, but would be nice if work automatically indeed

yup

could maybe ask in #C6QH853H8 even

yeah, maybe there is a cli workaroudn we don't know

The -T option is designed to run as a standalone tools, so not sure why that would be used with Clojure-LSP or anything other than the specific installed tool or tool alias. -T execution option removes all project paths except . by default

yep, for tools this makes sense, so that tool classpath is isolates from project code

maybe this use of clojure-lsp, to discover also the tool and project classpath together, is a bit unordinary :)

I would have thought https://clojure.org/guides/tools_build does what you need

No need to try do the same with clojure-lsp

Why do you even need to define paths here? If you don't specify paths at all for the alias, your entire project should be in the classpath because > -T includes the project root "." as a path by default. > - https://clojure.org/guides/tools_build#_setup

ah, I had utility code in a parent folder and also used some deps that aren't part of the project code

so the idea was to just gather a combined classpath for use for indexing with clojure-lsp, so you could say jump to definition from a build.clj file and still use clojure-lsp for project code such a combined classpath does not make sense when running a tools.build tool, that is a different usecase

might be issues with that kind of combined classpath even, now that I follow the trail of thought

If there is a reason to use the build aliases with Clojure-lsp, consider using the -X execution option

and use extra-paths and extra-deps in the alias definition

https://practical.li/blog/posts/clojure-which-execution-option-to-use/ may be of interest to understand the execution options

hmm, seems that :extra-paths is read by a clojure -T invocation, I assumed it would not be read

so the :extra-deps/paths could work

seems it does, this way I can get clojure-lsp to index project code and build code both, even build time deps that the project doesn't use 🙂