-
Notifications
You must be signed in to change notification settings - Fork 128
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
Custom repository for Scala artifacts not propagated to bloop #2802
Comments
I'm also encountering this. In the meantime, is it possible to set |
@TomasMikula is this the same issue with the sbt bridge or something else entirely? Bloop downloaded sbt bridges for a specific Scala version on demand and I think it doesn't have COURSIER_REPOSITORIES env variable set. @WojciechMazur Did you try setting the variable for the entire VM? Alternatively, to improve the situation we could set the env variable automatically when starting Bloop and if repositories were set. |
@tgodzik I wasn't aware of this env variable, setting it up seams to fix the problem, thank you. It might be a good usability feature if we wouldn't need to set env var up, especially since we need to also add the standard repositories as well, but I guess it requires a sever changes to Bloop. |
It's only an issue if you use a custom compiler version and it's a bit tricky to fix it otherwise. Probably, the easiest way to do it is to provide those env variables when starting bloop with non default repositories. |
Ah, upon inspecting the stack trace, it's a different problem:
Usually, artifacts are blocked if there's a known vulnerability. I will try to find out whether that's the case here. Sorry for the noise. |
Version(s)
1.2.0
Describe the bug
In the Open Community Build we're building and publishing the Scala 3 compiler artefacts to the custom repository. These artifacts are used to check if projects can be build against given versions of the compiler. It's invoked like:
When compiling with
--server=false
it works correctly, however, when running with bloop we get exception:Then investigating the logs you can see that custom repository
https://custom/maven/repo/...
was not included in the search of artifacts in the bloopTo Reproduce
Publish Scala 3 artifacts to custom remote repository, then try to use them in scala-cli
Expected behaviour
The custom repositories passed to the scala-cli should allow to find custom Scala 3 artefacts repositories.
The text was updated successfully, but these errors were encountered: