Jiří Mareš

But environment variable `COURSIER_REPOSITORIES` affect only coursier in `scala_cli`

And now it is not working with artifact proxy with self-signed certificate via https at all. Neither `COURSIER_REPOSITORIES` environment variable nor `repositories.default` scala-cli config. I don't know what to do...

Hi @Gedochao, I have been a little more investigating and it looks that problem is with https protocol with artifact proxy (not with its setting via COURSIER_REPOSITORIES or repositories.default). I...

From my point of view it directs to coursier that is run under the hood to resolve artifacts. But when run via scala-cli I can add `-Djavax.net.ssl.trustStore` but when run...

I have already raised one an the result is - it is not IDEA problem (https://youtrack.jetbrains.com/issue/SCL-22728/scala-cli-project-not-working)](https://youtrack.jetbrains.com/issue/SCL-22728/scala-cli-project-not-working)

But .. who starts the bloop server, from mine point of view it is started by scala-cli and IDEA in calling it via BSP? Therefore if the bloop is responsible...

No, I haven't ... be honest don't know how to make it. Just install Metals into VSC and run `scala-cli setup-id .` and open it in VSC? Or it is...

I try to make it but I am sorry not to test it now ... hope to make it this week. j

I have installed metals into VSC and have same result as in IDEA: ``` 024.06.28 15:33:28 INFO BSP server: [error] download error: Caught javax.net.ssl.SSLHandshakeException (PKIX path building failed: sun.security.provider.certpath.SunCertPathBuilderException: unable...

Yes, because of dylemma.xml-spac