Replies: 2 comments 1 reply
-
That should be possible. But you need to use a meta-build, so you can define the repositories in the Instead of // build.sc
import $meta._ // mill-build/build.sc
import mill._
import mill.runner.MillBuildRootModule
import coursier.core.Authentication
import coursier.maven.MavenRepository
object millbuild extends MillBuildRootModule {
def repositoriesTask: Task[Seq[Repository]] = T.task {
super.repositoriesTask() ++
MavenRepository(
"https://myrepo/releases-maven-local",
Some(Authentication(
T.env("MVN_REPOSITORY_USERNAME"),
T.env("MVN_REPOSITORY_PASSWORD")
))
)
}
} Edit: Corrected path and pseude code, based on the feedback. |
Beta Was this translation helpful? Give feedback.
0 replies
-
Thanks that worked - there where some problems with your snippets though.
|
Beta Was this translation helpful? Give feedback.
1 reply
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
I want to migrate my Ammonite Script to a Mill Plugin (External Module).
The Problem I have is, that it has to be in a private Repo (Not Maven Central).
In Ammonite this is done like this:
Is there a way I can do this with Mill?
I tried also with the Coursier Environment variables. The Repo was listed but the credentials did not to work (401 Unauthorized).
https://get-coursier.io/docs/other-credentials
Beta Was this translation helpful? Give feedback.
All reactions