sbt-api-mappings
An Sbt plugin that fills apiMappings for common Scala libraries. (by ThoughtWorksInc)
sbt-revolver
An SBT plugin for dangerously fast development turnaround in Scala (by spray)
Our great sponsors
sbt-api-mappings | sbt-revolver | |
---|---|---|
- | 2 | |
90 | 840 | |
- | -0.2% | |
4.2 | 3.1 | |
about 2 months ago | about 1 year ago | |
Scala | Scala | |
Apache License 2.0 | 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.
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.
sbt-api-mappings
Posts with mentions or reviews of sbt-api-mappings.
We have used some of these posts to build our list of alternatives
and similar projects.
We haven't tracked posts mentioning sbt-api-mappings yet.
Tracking mentions began in Dec 2020.
sbt-revolver
Posts with mentions or reviews of sbt-revolver.
We have used some of these posts to build our list of alternatives
and similar projects. The last one was on 2022-01-10.
-
Tooling question
Another thing to look into is sbt-revolver, this will shorten the turnaround time on whatever machine is running sbt. I remember it being pretty helpful when I was working with scala.js. Good luck!
-
Friction-less scala - Tell us what is causing friction in your day-to-day life with Scala
SBT. It's not because of the pseudo-scala config language, that looks especially alien next to braceless Scala 3 code. Or the weird symbolic operators. The big problem is correctness; in almost every project I've had to use spray-resolver because I've encountered weird bugs because SBT reuses the same dirty JVM. I really thing Drip would help here. I'll keep using SBT because it has the best Scala ecosystem support and great plugins like sbt-crossproject. It would also be great to be able to write build.sbt files in modern, regular Scala.
What are some alternatives?
When comparing sbt-api-mappings and sbt-revolver you can also consider the following projects:
sbt-robovm - An sbt plugin for iOS development in Scala
coursier - Pure Scala Artifact Fetching
sbteclipse - Plugin for sbt to create Eclipse project definitions
sbt-play-scalajs - SBT plugin to use Scala.js along with any sbt-web server.
sbt-dependency-graph - sbt plugin to create a dependency graph for your project
sbt-native-packager - sbt Native Packager
sbt-docker - Create Docker images directly from sbt
sbt-pantarhei - sbt plugin building and publishing release notes from github pull requests
xsbt-web-plugin - Servlet support for sbt
scala-clippy - Good advice for Scala compiler errors
sbt-api-mappings vs sbt-robovm
sbt-revolver vs coursier
sbt-api-mappings vs sbteclipse
sbt-revolver vs sbt-play-scalajs
sbt-api-mappings vs sbt-dependency-graph
sbt-revolver vs sbt-dependency-graph
sbt-api-mappings vs sbt-native-packager
sbt-revolver vs sbt-docker
sbt-api-mappings vs sbt-pantarhei
sbt-revolver vs xsbt-web-plugin
sbt-api-mappings vs coursier
sbt-revolver vs scala-clippy