-
-
Notifications
You must be signed in to change notification settings - Fork 337
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
The classpath for BSP when using the mill dev.launcher
is too long
#962
Comments
The long classpath is coming from here https://github.com/lihaoyi/mill/blob/8cd135ad640b2732462739f6b104df4d3ac7edc1/contrib/bsp/src/mill/contrib/BSP.scala#L74-L76 The shell script generated by I think the BSP install command should do something similar to what Mill's Maybe the best solution is to have Edit: I don't think the above would help. It looks to me like the BSP command is actually expecting I think the question is if there's a better way for Mill to tell the BSP command how to start Mill. An option could be for Mill's boot scripts to pass their own location to the Mill process as a system parameter. For now the workaround is probably to avoid using BSP when starting off a |
Raised a PR with a first attempt at a solution. Edit: Not sure how best to solve this. If the Mill script path is generally useful, maybe it should be a parameter to the Evaluator. The script could pass it into MillMain, and put it in the Evaluator, where BSP could read it. If the script path isn't useful to anything other than BSP, maybe it is better to just close this issue as wontfix, since it's just a minor inconvenience during development of Mill. The workaround is to use |
Mill's BSP server isn't designed to be run via |
Hi,
When I set up BSP using
mill.contrib.BSP/install
, from a mill launcher generated withmill dev.launcher
, the generated BSP file (.bsp/mill.json) contains an extremely long classpath string, which prevents IntelliJ from loading the project.This command is too long for IntelliJ to run, which causes IntelliJ to fail to open the project properly
When using a regular Mill release, the corresponding string is much smaller
Would an option be for the
dev.launcher
command to put the dependency jars in a directory somewhere, so they can be referenced with a wildcard in the classpath?The text was updated successfully, but these errors were encountered: