ScalaKata2 VS sbt-mima-plugin

Compare ScalaKata2 vs sbt-mima-plugin and see what are their differences.

ScalaKata2

Interactive Playground (by MasseGuillaume)

sbt-mima-plugin

A tool for catching binary incompatibility in Scala (by lightbend)
Our great sponsors
  • WorkOS - The modern identity platform for B2B SaaS
  • InfluxDB - Power Real-Time Data Analytics at Scale
  • SaaSHub - Software Alternatives and Reviews
ScalaKata2 sbt-mima-plugin
- 2
101 449
- 0.9%
0.0 7.7
about 7 years ago 7 days ago
Scala Scala
- Apache License 2.0
The number of mentions indicates the total number of mentions that we've tracked plus the number of user suggested alternatives.
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.

ScalaKata2

Posts with mentions or reviews of ScalaKata2. We have used some of these posts to build our list of alternatives and similar projects.

We haven't tracked posts mentioning ScalaKata2 yet.
Tracking mentions began in Dec 2020.

sbt-mima-plugin

Posts with mentions or reviews of sbt-mima-plugin. We have used some of these posts to build our list of alternatives and similar projects. The last one was on 2023-09-07.
  • Semver violations are common, better tooling is the answer
    7 projects | news.ycombinator.com | 7 Sep 2023
    In the Scala ecosystem, MiMa [1] has been in widespread use for years. It automatically checks compatibility for the binary API of a library. Every library with any amount of success uses it. One could say it's the foundation of a stable ecosystem. We also have sbt-version-policy [2] to set it up with minimal configuration (and directly relate it to SemVer).

    More recently, we got tasty-mima [3], which checks compatibility at the type system level, rather than the binary level.

    [1] https://github.com/lightbend/mima

    [2] https://github.com/scalacenter/sbt-version-policy

    [3] https://github.com/scalacenter/tasty-mima

  • sbt/scalatest library or plugin that only re-runs tests for code that changed
    2 projects | /r/scala | 23 Jul 2022
    Off the top of my head, a naive & approximate solution would be to use test coverage to find out which tests test which blocks of code. Then, when a binary, syntactic incompatibility is detected, re-run only these tests captured for that piece of code.

What are some alternatives?

When comparing ScalaKata2 and sbt-mima-plugin you can also consider the following projects:

sbt-site - Site generation for sbt

mdoc - Typechecked markdown documentation for Scala

sbt-ensime

sbt-header - sbt-header is an sbt plugin for creating file headers, e.g. copyright headers

sbt-native-packager - sbt Native Packager

sbt-revolver - An SBT plugin for dangerously fast development turnaround in Scala

sbt-scoverage - sbt plugin for scoverage

sbt-pack - A sbt plugin for creating distributable Scala packages.

sbt-release - A release plugin for sbt

sbt-updates - sbt plugin that can check Maven and Ivy repositories for dependency updates

sbt-sonatype - A sbt plugin for publishing Scala/Java projects to the Maven central.