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
As a follow-up to the recent Scala Tooling Summit I wanted to raise a few questions/requests that we can maybe start digging into and tracking here. Across the ecosystem we have various ways of publishing. sbt has it's own implementation, Mill has it's own, and now this is repo's implementation is being used in scala-cli. How could we possibly better utilize this (if we'd all agree on that) in various places. Here are some question/topics that came up during the summit.
What's the dependency chain look like in this repo? Are there any that are non-essential? For some of them, would it make sense to make an interface and allow the various tools to provide their own JSON library for example.
Could some documentation be written for this?
There seems to be no tests in this repo?
The text was updated successfully, but these errors were encountered:
As a follow-up to the recent Scala Tooling Summit I wanted to raise a few questions/requests that we can maybe start digging into and tracking here. Across the ecosystem we have various ways of publishing. sbt has it's own implementation, Mill has it's own, and now this is repo's implementation is being used in scala-cli. How could we possibly better utilize this (if we'd all agree on that) in various places. Here are some question/topics that came up during the summit.
The text was updated successfully, but these errors were encountered: