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

Allow custom repositories #30

Open
fourth44 opened this issue Jul 14, 2022 · 2 comments
Open

Allow custom repositories #30

fourth44 opened this issue Jul 14, 2022 · 2 comments

Comments

@fourth44
Copy link

It would be great to define custom ivy/nexus repositories.
Ideally, this configuration would live in some global config file (i.e. ~/.scala-update/config.hocon?)
Perhaps there is some coursier global config for this to piggy-back on?

Imagine a company with a lot of interdependent projects and a private nexus repository.
Ideally, I would have set up an instance of scala-steward long ago, but it's simply to much of a hassle. Scala-update is ideal (apart from requiring to be run manually) as it doesn't need much config or resources to run. However, currently, non-public dependencies are ignored, it would be excellent to configure the local nexus repo.

@ex0ns
Copy link
Contributor

ex0ns commented Mar 17, 2023

This issue is pretty old, however it seems that as this is using coursier under the hood, the COURSIER_REPOSITORIES variable is correctly used, I tested it today and it worked fine.

Be aware that the native image is built with a cacert and does not use the runtime cacerts, so you might run into some issues with the native-image version if you are using a custom CA.

@kitlangton
Copy link
Owner

Unfortunately, I don't have much time to try this myself, but I'm completely open to any attempts :D

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants