Repository navigation
Conversation
ivantopo
force-pushed
the
migrate-build-to-mill
branch
from
September 4, 2026 13:50
62adfde to
77cdd71
Compare
ivantopo
force-pushed
the
migrate-build-to-mill
branch
from
September 4, 2026 14:03
77cdd71 to
79aad9f
Compare
ivantopo
force-pushed
the
migrate-build-to-mill
branch
from
October 14, 2026 13:26
e6cf08b to
63ddbb6
Compare
Keep annotation's shaded libraries as provided dependencies and declare them explicitly for tests. Share publishing metadata across Scala modules, the annotation API, and the BOM. Enforce Scala formatting in CI.
ivantopo
force-pushed
the
migrate-build-to-mill
branch
3 times, most recently
from
October 15, 2026 11:55
aadef9a to
e0420cd
Compare
ivantopo
force-pushed
the
migrate-build-to-mill
branch
from
October 19, 2026 19:11
e0420cd to
e550fc8
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
This is very WIP. Don't bother too much looking at this.
I have been using Mill for other projects in the last year and IMHO the developer experience is considerably better once you get used to how the tasks are organized. More importantly, every time I needed to do something special with other Mill builds it was simpler to reason about the dependencies, how things are done in Mill, and how to make the adjustments I needed. I have 13+ years of using SBT and <1 year with Mill made me want to change and not look back. SBT served us well, but I don't want to use it anymore.
I don't have the energy and patience to make this a gradual migration with parallel SBT/Mill builds and we are going full big bang on this change.
Interesting changes and findings (will continue to update as I finish the process):
provideddependencies so we will not be bumping the versions our users have in their classpaths.