Skip to content
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

Setting repositories using config repositories.default affects also local sbt #3231

Open
jiramares opened this issue Oct 18, 2024 · 2 comments
Labels
bug Something isn't working config Issues tied to the config sub-command. coursier Issues tied with coursier integration. requires scoping Issue requires a spike to revalidate it and assign an up-to date scope for its requirements.

Comments

@jiramares
Copy link

Scala CLI version: 1.5.1

Setting default repositories using command scala-cli --power config repositories.default ivy2local https://out.server/repos/maven-proxy affect also repositories for sbt. It is expected behaviour.

It should change repositories only for scala-cli as performs setting environment variable COURSIER_REPOSITORIES.

@jiramares jiramares added the bug Something isn't working label Oct 18, 2024
@Gedochao
Copy link
Contributor

Likely caused by the same thing as:

The repository config is shared between scala-cli and coursier, and SBT uses coursier under the hood as well... 😕

@Gedochao Gedochao added requires scoping Issue requires a spike to revalidate it and assign an up-to date scope for its requirements. coursier Issues tied with coursier integration. config Issues tied to the config sub-command. labels Oct 18, 2024
@jiramares
Copy link
Author

But environment variable COURSIER_REPOSITORIES affect only coursier in scala_cli

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working config Issues tied to the config sub-command. coursier Issues tied with coursier integration. requires scoping Issue requires a spike to revalidate it and assign an up-to date scope for its requirements.
Projects
Status: To do
Development

No branches or pull requests

2 participants