Bug#1125161: Re-bootstrapping sbt and modern Scala; the Scala 3 path is now open
Juan M. Méndez Rey
juan.mendezr at proton.me
Fri Jun 12 15:33:02 BST 2026
> The problem is that most Scala packages are built using sbt or mill, and nothing you can do (to my knowledge) will make sbt or mill ignore maven and use .deb installed libraries.
>
> Likewise with any scala-cli scripts.
>
> So unless you can solve the centralized cache problem and force all build systems to use it you are not going to be able to do it your way.
sbt, scala-cli can be forced to ignore maven central and resolve everything from one local repository, offline with Dsbt.override.build.repos=true, and adding a repositories file
e.g.:
[repositories]
debian: file:///usr/share/maven-repo
What I can see from your point is the cost: each application still needs its whole dependency tree packaged at compatible versions, but still having the compiler and core libraries are a finite job and the foundation for the rest.
I might be missing something though, let me know if you anything wrong.
Juan
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://alioth-lists.debian.net/pipermail/pkg-java-maintainers/attachments/20260612/6dddae53/attachment.htm>
More information about the pkg-java-maintainers
mailing list