Mill and VSCode

[charpov]

I'm trying to use VSCode on a Mill project created via ./mill init javalib/basic/2-module-deps. The import and indexing happen and Metals looks happy enough (no error in the logs):

However, VSCode cannot see the dependencies.

Any idea what is going on? (I'm an IntelliJ user without much VSCode experience.)

[charpov]

I posted the same question in a Metals forum, and this is the reply I got:

Thanks for reporting! The errors that you are seeing are from the Java plugin, not from Metals. I don't think that Java plugin is able to work with mill currently (unless there is some eclipse export from mill).

I suggest that you disable the Java plugin in this workspace.

Is that true? That makes Mill pretty much unusable in Java projects for VSCode users.

[lefou]

Mill has some eclipse support. You can generate the usual project files (.project, .classpath) for each projects with mill mill.eclipse/. See https://mill-build.org/mill/cli/installation-ide.html#_eclipse_ide

I don't use Java language servers, but I think some may support these files. If you try it, please report back your findings.

[charpov]

I tried that, and it works.
I'm still being prompted as to whether to use the build server:

Should I? Will VSCode benefit from that? VSCode seems to be building in bin and Mill in out, so I'm wondering if the LSP is leveraged at all.

[charpov]

I marked the question as answered, but I'm still curious about the proper use of metals in this case. This is probably a question for an actual VSCode user...