-
Notifications
You must be signed in to change notification settings - Fork 121
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Plugins clearout #4356
Plugins clearout #4356
Conversation
since sbt 1.3.0 this is builtin to sbt, no need for plugin any more
we don't use assembly any more, the last usage was removed over 3 yrs ago so this can go
// Currently multiple modules depend on scala-java8-compat, some on 0.8.x, 0.9.x and 1.x.y | ||
// These may be binary incompatible, but force the checker to accept them | ||
// In the future, check if this override can be removed | ||
ThisBuild / libraryDependencySchemes += | ||
"org.scala-lang.modules" %% "scala-java8-compat" % VersionScheme.Always |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It looks like sbt-coursier
was suppressing these warnings; this one popped up when it was removed.
Seen on auth, usage, image-loader, metadata-editor, thrall, leases, cropper, media-api, kahuna (merged by @andrew-nowak 8 minutes and 47 seconds ago) Please check your changes! |
Seen on collections (merged by @andrew-nowak 8 minutes and 52 seconds ago) Please check your changes! |
What does this change?
Remove some unused sbt plugins, notably the
sbt-coursier
plugin which has some bugs which interferes with sbt's own dependency resolution behaviours.How should a reviewer test this change?
Should be a no-op, with no change in behaviour when deployed
How can success be measured?
Who should look at this?
Tested? Documented?