You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When running Mill in an environment that can access Maven Central artifacts without authentication, build.sc scripts that use import $ivy statements and ivyDeps work correctly.
When running Mill in an environment that has to authenticate with the artifact repository, build.sc scripts fail to retrieve the requested artifacts. This is true for import $ivy statements, ivyDeps, and other artifacts that Mill is trying to fetch for itself.
In both kinds of environment, plain Ammonite scripts work correctly.
Note: Between each of the various experiments below, I throw away the Mill out directory and the Coursier cache directory to simulate an initial environment.
Note: Host artifactory.example.com is used in the examples below in place of the real Artifactory server that I connected to. It mirrors Maven Central, but requires authentication.
When running Mill in an environment that can access Maven Central artifacts without authentication,
build.sc
scripts that useimport $ivy
statements andivyDeps
work correctly.When running Mill in an environment that has to authenticate with the artifact repository,
build.sc
scripts fail to retrieve the requested artifacts. This is true forimport $ivy
statements,ivyDeps
, and other artifacts that Mill is trying to fetch for itself.In both kinds of environment, plain Ammonite scripts work correctly.
Given the following:
.mill-version
build.sc
plain.sc
Note: Between each of the various experiments below, I throw away the Mill
out
directory and the Coursier cache directory to simulate an initial environment.In an unrestricted environment:
Mill behaves correctly...
and Ammonite behaves correctly...
In a restricted environment:
Note: Host artifactory.example.com is used in the examples below in place of the real Artifactory server that I connected to. It mirrors Maven Central, but requires authentication.
Note: No credentials have been provided to Coursier.
Mill fails to get the JARs it needs. This is expected...
Ammonite also fails. This is also expected...
Now with the correct credentials provided to Coursier. (In my experiment I set this variable with the correct values, the text below has fake values.)
Ammonite successfully gets the JARs it needs...
... but Mill does not. This is a scenario that I believe should work correctly.
The text was updated successfully, but these errors were encountered: