This repository has been archived by the owner on Jun 2, 2022. It is now read-only.
WIP - upgrade to sbt 1.0 #144
Merged
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
|
Congratulations on getting to sbt 1.0. I don't even want to think about doing that for |
|
I'm not convinced we want to move yet. I'm messing around with it in doobie and it's behaving strangely. |
|
Sbt and strange behavior is the regular state 😄. I guess for doobie you don't need to cross-sbt build but maybe for tut? |
|
We had to fork tut. There was no way to make it compile for 0.13 and 1.0 |
|
sbt 1.0.3 fixes the issues I ran into, and all the plugins are now available so I think we can merge this if it goes green. |
|
Hm wonder why scalastyle just now saw that stuff. |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
I don't think our build will need any changes other than updating the plugins.