Improve the error message for when coursier cannot fetch a JVM for Bloop #3146
Labels
Bloop
Issues tied with Bloop integration.
enhancement
New feature or request
os:BSD
Issues tied with BSD operating systems integration
reporting
Issues tied with error and warning reporting.
Is your feature request related to a problem? Please describe.
On systems for which there is no Java 17+ listing in Coursier's jvm-index, if the JVM isn't provided on Scala CLI startup (i.e. via an environment variable), the error we are printing seemingly coming straight from Coursier) is quite cryptic, and it's not indicating what the user should do in any way. OpenBSD is an example of such an OS.
Describe the solution you'd like
We need a better error message, optimally explaining to the user what he could do to make Scala CLI work.
The workaround of using
--server=false
should also be suggested.Describe alternatives you've considered
We could try to improve the
jvm-index
system coverage, but that's tricky and there's always some niche OS that we won't be able to cover and its (power) users would still have to set up the JVM themselves.Additional context
Extracted out of:
The text was updated successfully, but these errors were encountered: