Skip to content
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

Use millw launcher instead of running mill by cs #1375

Merged
merged 1 commit into from
Sep 20, 2022

Conversation

lwronski
Copy link
Contributor

When IntelliJ import scala-cli BSP project it creates mill-bsp.json with long path to mill, because coursier update java.class.path and set there all jar dependencies from mill. To fix it, scala-cli uses millw launcher which doesn't have so long java.class.path.

Mill read path to launcher from java.class.path.

@lwronski lwronski force-pushed the fix-idea-import-mill-bsp-json branch 4 times, most recently from 9940d14 to eec420e Compare September 20, 2022 08:14
@lwronski lwronski marked this pull request as ready for review September 20, 2022 09:12
mill Outdated Show resolved Hide resolved
When IntelliJ import scala-cli BSP project it creates mill-bsp.json with long path to mill, because coursier update java.class.path and set there all jar dependencies from mill. To fix it, scala-cli uses millw launcher which doesn't have so long java.class.path.
@lwronski lwronski enabled auto-merge (squash) September 20, 2022 09:25
@lwronski lwronski merged commit 72ca7c7 into VirtusLab:main Sep 20, 2022
@Gedochao Gedochao added the DX Dev experience label Sep 21, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
DX Dev experience
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Fix the IDEA IntelliJ BSP import of the mill build for the scala-cli repository
3 participants