sbt-dependency-updates' dependencyUpdates task has the same name as sbt-updates' dependencyUpdates which means that one task is shadowed by the other if both plugins are installed in a project. We hit this problem in scala-steward in projects that use sbt-dependency-updates (see https://github.com/fthomas/scala-steward/issues/178#issuecomment-443878634 for details). Would you consider renaming your dependencyUpdates so that both plugins can be installed in a project without causing any conflict?
sbt-dependency-updates'
dependencyUpdates
task has the same name as sbt-updates'dependencyUpdates
which means that one task is shadowed by the other if both plugins are installed in a project. We hit this problem in scala-steward in projects that use sbt-dependency-updates (see https://github.com/fthomas/scala-steward/issues/178#issuecomment-443878634 for details). Would you consider renaming yourdependencyUpdates
so that both plugins can be installed in a project without causing any conflict?