Closed amorfis closed 4 years ago
Thanks for creating this issue! Do you have any other plugins enabled? I feel like this could be related to dependency resolution conflicts in plugins. If not, would it be possible to provide a sample repository where this issue is demonstrated?
I have many plugins, the list below:
addSbtPlugin("com.softwaremill.sbt-softwaremill" % "sbt-softwaremill" % "1.3.16")
addSbtPlugin("com.geirsson" % "sbt-scalafmt" % "1.5.1")
addSbtPlugin("com.typesafe.sbt" % "sbt-native-packager" % "1.3.6")
addSbtPlugin("com.github.gseitz" % "sbt-release" % "1.0.11")
addSbtPlugin("com.mintbeans" % "sbt-ecr" % "0.14.1")
addSbtPlugin("org.scoverage" % "sbt-scoverage" % "1.5.1")
addCompilerPlugin("io.tryp" % "splain" % "0.4.1" cross CrossVersion.patch)
addSbtPlugin("com.updateimpact" % "updateimpact-sbt-plugin" % "2.1.3")
addSbtPlugin("net.virtual-void" % "sbt-dependency-graph" % "0.9.0")
I can't share my repository with you, sorry, it's client's code. Maybe later I'll create some. Thank you!
The first thing I notice is sbt-scalafmt
which depends on scalameta v1.7.0. That could be the issue (note that since v2.0.0 scalafmt falls under a different groupId).
By the way, I noticed you work at softwaremill. I'm replacing the http client we currently use with sttp in #299 and it is awesome 😁
I had no idea scalafmt changed the group id! Thanks!
It's great you use sttp, thanks! I agree it's awesome :) It's a small world, isn't it :)
It works with new scalafmt
Good to hear!
Summary
I added the Stryker4s plugin to my project, but when I run
sbt stryker
the error occurs:Is this some wrong scala-meta version? I don't know how to change it.
Stryker4s config
I didn't change the config file, using defaults.
Stryker4s environment
Your Environment