v1.0.4
Hotfix for buildTarget/jvmRunEnvironment in BSP
We've addressed a bug that surfaced when opening your ScalaCLI projects in Metals or IntelliJ. If you encountered the following log:
2023.08.09 15:48:34 INFO BSP server: Caused by: java.lang.IllegalArgumentException: Type ch.epfl.scala.bsp4j.JvmMainClass is instantiated reflectively but was never registered. Register the type by adding "unsafeAllocated" for the type in reflect-config.json.
2023.08.09 15:48:34 INFO BSP server: at com.oracle.svm.core.graal.snippets.SubstrateAllocationSnippets.instanceHubErrorStub(SubstrateAllocationSnippets.java:309)
2023.08.09 15:48:34 INFO BSP server: at [email protected]/sun.misc.Unsafe.allocateInstance(Unsafe.java:864)
2023.08.09 15:48:34 INFO BSP server: ... 36 more
those logs should no longer appear. Thanks to @lwronski for providing the fix in #2342.
What's Changed
- Update scala-cli.sh launcher for 1.0.3 by @github-actions in #2338
- Add missing note to release notes about rename parameter by @lwronski in #2340
- Back port of documentation changes to main by @github-actions in #2341
- Fix - support jvmRunEnvironment request for native launcher of scala-cli by @lwronski in #2342
- 1.0.4 release notes by @lwronski in #2343
Full Changelog: v1.0.3...v1.0.4