Support `mimaReportBinaryIssues / skip`

As in publish / skip := true and friends, as a way to disable this task.

We’ve currently implemented this in https://github.com/typelevel/sbt-typelevel/pull/117#discussion_r795113203 to help accommodate build matrices with holes in them, where certain modules are not available for certain Scala versions.

Is this something you’re open to? I can try and help with a PR. Thanks!

[dwijnand]

You can do it for all the default tasks, obviously. And for other keys like mimaPreviousArtifacts you can still access them by name (SettingKey[Set[ModuleID]]("mimaPreviousArtifacts")).

Things get harder when their keys use their own types, but it’s possible:

Def.settings {
  try {
    val clazz = Class.forName("sbt.nio.Keys$WatchBuildSourceOption")
    val value = Class.forName("sbt.nio.Keys$IgnoreSourceChanges$").getDeclaredField("MODULE$").get(null)
    val manifest = new scala.reflect.Manifest[AnyRef]{ def runtimeClass = clazz }
    Seq(
      SettingKey[AnyRef]("onChangedBuildSource")(manifest, sbt.util.NoJsonWriter()) in Global := value
    )
  } catch {
    case e: Throwable =>
      Nil
  }
}

[raboof]

This PR introduces a custom +~ command that fixes both these limitations

Sounds cool, but I stopped reading there 😃 ideally sbt would support this out-of-the-box

Hehe that’s fair 😉. I think the +~ wasn’t really needed to make the build work though, only to re-introduce the functionality we previously implemented using scalaVersion :=.

but for now skip seems like it can get us close for 99% of use-cases.

👍 😉