steps
- Set
-Dsbt.boot.directory=<some_path> in SBT_OPTS env variable,
- run
sbt bspConfig,
- run the args generated in the config
sbt.json, which in my case look like this: [...]/java -Xms100m -Xmx100m -classpath [...]/sbt-launch.jar -Dsbt.script=[...]/sbt xsbt.boot.Boot -bsp.
problem
-Dsbt.boot.directory=<some_path> option doesn't seem to be propagated to args generated in the bsp config, and the launcher starting the sbt server uses the default sbt.boot.directory.
expectation
SBT_OPTS to be propagated to the generated bsp config where relevant and possibly add the necessary args to the generated config:
[...]/java -Xms100m -Xmx100m -classpath [...]/sbt-launch.jar -Dsbt.script=[...]/sbt -Dsbt.boot.directory=<some_path> xsbt.boot.Boot -bsp
notes
connected to: scalameta/metals#5796
steps
-Dsbt.boot.directory=<some_path>inSBT_OPTSenv variable,sbt bspConfig,sbt.json, which in my case look like this:[...]/java -Xms100m -Xmx100m -classpath [...]/sbt-launch.jar -Dsbt.script=[...]/sbt xsbt.boot.Boot -bsp.problem
-Dsbt.boot.directory=<some_path>option doesn't seem to be propagated to args generated in the bsp config, and the launcher starting the sbt server uses the defaultsbt.boot.directory.expectation
SBT_OPTSto be propagated to the generated bsp config where relevant and possibly add the necessary args to the generated config:[...]/java -Xms100m -Xmx100m -classpath [...]/sbt-launch.jar -Dsbt.script=[...]/sbt -Dsbt.boot.directory=<some_path> xsbt.boot.Boot -bspnotes
connected to: scalameta/metals#5796