Replies: 3 comments 1 reply
-
Technically, all So, let me ask, do you already have some specific lock file format in mind, which we should produce? Is there already some lock file format which coursier or nix understands? If not, it would be helpful to gather some information about what we should put in such a file. The lockfile generator could be implemented as a external module, since all targets providing ivyDeps are more or less introspectable. (The |
Beta Was this translation helpful? Give feedback.
-
May relate to coursier/coursier#1487 |
Beta Was this translation helpful? Give feedback.
-
I came across this issue again: ivy hash changed silently after one or two month and invalidates our caches....
[
{
"coord": "org.scala-lang:scala-library:2.13.1",
"url": "https://repo1.maven.org/maven2/org/scala-lang/scala-library/2.13.1/scala-library-2.13.1.jar",
"sha256sum": "711dcb0ba3d8d8392a52162c1f251d89787148981d2823e30697bc08282521ae",
},
] I prefer your second approach, "Implement the same in Mill directly", my concerns are:
In my mind, I think this might be possible:
|
Beta Was this translation helpful? Give feedback.
-
In many build flows, reproducibility and offline building is important.
I wonder if it would be possible to provide a tool from mill to expose all ivy as json as the lock file. Later we can use this file to download all ivy dependencies w/ coursier to prepare the build artifacts for no network building.
A dirty hack has been achieved in our nix flow:
https://github.com/chipsalliance/t1/blob/master/nix/pkgs/mill-builder.nix
Beta Was this translation helpful? Give feedback.
All reactions