-
Notifications
You must be signed in to change notification settings - Fork 137
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
-Djavax.net.ssl.trustStore
certs not properly passed when downloading deps in BSP
#2963
Comments
And now it is not working with artifact proxy with self-signed certificate via https at all. Neither |
Hey, I'll try to tackle this soon (likely won't be this week, however). |
Hi @Gedochao, |
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 |
Definitely Scala CLI/Bloop, depending on which dependencies. Both use Coursier under the hood.
@jiramares Can you raise a corresponding ticket on the JetBrains issue tracker? (https://youtrack.jetbrains.com/issues) |
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 for resolving why it is run okay through scala-cli and not running via IDEA? I am confused.... |
One extra question - have you tried running it in Metals? I hope we won't end up bouncing this back and forth... |
No, I haven't ... be honest don't know how to make it. |
Exactly this. |
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:
Looks like that the |
@jiramares do you use cats within your project? |
Yes, because of dylemma.xml-spac |
My guess is that we are not adding the certs when downloading sources somehow, but it seems unexpected 🤔 |
-Djavax.net.ssl.trustStore
not properly passed when downloading deps in BSP
-Djavax.net.ssl.trustStore
not properly passed when downloading deps in BSP-Djavax.net.ssl.trustStore
certs not properly passed when downloading deps in BSP
@jiramares are you still encountering this issue with Scala CLI v1.5.1? |
It is still not working. If I repeat the steps in issue description I am getting following stacktrace:
it looks like the problem is with coursier that is running its own JDK and we have to somewhere specify PS. The PS2. I am a little bit confused because the file PS3. If I removed this environment variable the value |
Did you do |
@tgodzik That's it ... it works. Great .... I am going to try to finalize solution based on it. |
Versions
Scala CLI version: 1.3.2
Scala version (default): 3.4.2
IntelliJ IDEA 2024.1.3 (Ultimate Edition)
Build #IU-241.17890.1, built on June 4, 2024
Description
We used company artifactory to resolve/cache artefacts. Therefor I have to set up environment varianble
COURSIER_REPOSITORIES
to handle it right. Because we are using self signed certificate on server there is problem with resolving artefacts directly using coursier (upgrades scala-cli, scala or java).I realized that there is config
repositories.default
that seems to me to fulfil the same thing but only for scala-cli (not system wide). So I started using it. It works well but breaks the integration with IDE.After starting using
repositories.default
instead ofCOURSIER_REPOSITORIES
I can't build in IDEA via BSP. In BSP window there has been no tree under the root of project. The problem is with our artifactory server with self signed certificate because using maven central causes everything works fine.To Reproduce
scala-cli config repositories.default ivy2local https://our-server/with-self-signed-certificate/repo --power
test
test.sc
with contenttest
runscala-cli setup-ide test.sc
In BSP window there is no tree and println is marked as uknown symbol.
Expected behaviour
There should be dependencies in BSP window and println shoul be known.
The text was updated successfully, but these errors were encountered: