Skip to content

Conversation

przemek-pokrywka
Copy link

The ivy2Local predefined repository is most useful when you publish local artifacts with SBT.

Sometimes you work on a large application built with SBT, yet you still want to write scripts that use a part of the application's logic. Then you can publish your application's artifacts from SBT with publishLocal and then consume these artifacts from scala-cli using scala-cli --repository ivy2Local --dep myapp::artifact:1.0-SNAPSHOT

The ivy2Local predefined repository is most useful when you publish local artifacts with SBT.
@Gedochao
Copy link
Contributor

The reference part of the docs is mostly generated from code, so you have to change it there, and then regenerate the docs with

./mill -i 'generate-reference-doc[]'.run

as per https://github.com/VirtusLab/scala-cli/blob/main/CONTRIBUTING.md#rules-for-a-well-formed-pr

The relevant piece of code, where this doc actually lives:

|Accepts predefined repositories supported by Coursier (like `sonatype:snapshots` or `m2Local`) or a URL of the root of Maven repository""".stripMargin

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

Successfully merging this pull request may close these issues.

2 participants