Migrate project to use sbt-typelevel #665
Open
Conversation
This file contains 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
armanbilge
reviewed
Mar 25, 2022
DavidGregory084
force-pushed
the
migrate-sbt-typelevel
branch
from
c682a9c to
5fb5d55
Compare
DavidGregory084
force-pushed
the
migrate-sbt-typelevel
branch
from
5fb5d55 to
e2972fb
Compare
armanbilge
reviewed
Jun 6, 2022
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 migrates the project to use sbt-typelevel.
If it's decided to put the project forward as a Typelevel incubator project it might be good to do this anyway.
It also fixes the problems with doc generation that @lewisjkl saw since sbt-typelevel sets the
apiURLfor the project to ensure that cross-module API doc linking works.A few other notable things:
Contributed on behalf of the @opencastsoftware open source team. 👋