Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Ticks off #1826 (comment)
mill.modules
is a very confusing name that I came up with very early in Mill's development. It misleadingly has nothing to do withmill.Module
, and is just a grab bag of helpers. This PR moves them to the JVM packages which are most related to their functionalityWe basically move the following files:
mill.modules.Assembly
->mill.scalalib.Assembly
mill.modules.Util
->mill.util.Util
mill.modules.Jvm
->mill.util.Jvm
mill.modules.CoursierSupport
->mill.util.CoursierSupport
There is probably further cleanup and re-organization we can do here. Currently,
Util
andJvm
are pretty tightly coupled together, withVisualizeModule
living inmain
stopping us from moving them all toscalalib
. An alternative is to moveAssembly
tomill.util
, so at leastcreateJar
andcreateAssembly
can live in the same package rather than being split acrossmill.{util,scalalib}
.But for now, just breaking up
mill.modules
should already be a step forward, and further cleanups can come in follow up PRs