Łukasz Wroński

> I'm confused, the desciption says you're adding the `code` field, but the PR adds a `data` field (also in spec) and a `dataKind` (which we use in BSP, but...

@milessabin Thanks for reporting, Scala CLI uses bloop which requires java 17 or higher to start. If you pass `--bloop-jvm system`, scala-cli search java >= 17 on PATH and if...

@milessabin Now, scala-cli uses fork bloop - https://github.com/scala-cli/bloop-core, which drop support for Java < 17.

`scala-cli` won't be able to detect java installed if `JAVA_HOME` not exits on the`PATH`. User may have multiple versions of java installed, and it is up to the user to...

Hi @benwbooth, What do you mean by adding a script search path feature? If I understand correctly, Scala CLI should support the new environment variable `SCALAPATH`, which contains a list...

@mpkocher For now, scala-cli doesn't support `SCALAPATH`. I agree, that it huge semantics change to scala-cli so it requires more discussion. Now, scala-cli users can use `file` directive to define...

Fixed by #1539.

@dxxvi, If you have Java 17 or a newer version already installed and available on the PATH, scala-cli will automatically detect and use it without the need for any additional...

> Trying to open a 2.13 repl on Java 11 using the command `scala-cli -S 2.13.0 -j 11` gives me the error > > ``` > Error: java.lang.Exception: java.lang.Exception: Error...

Hi, I'd like to provide an updated summary on this issue, as there are newer and more user-friendly ways to set JVM properties in `scala-cli`. 1. Direct Setting with `-D`...