sbt-dependency-graph
sbt plugin to create a dependency graph for your project [Moved to: https://github.com/sbt/sbt-dependency-graph] (by jrudolph)
apply-at-vdb
By kgrunert
sbt-dependency-graph | apply-at-vdb | |
---|---|---|
1 | 1 | |
1,216 | 0 | |
- | - | |
1.2 | 4.0 | |
over 3 years ago | 4 months 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.
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-dependency-graph
Posts with mentions or reviews of sbt-dependency-graph.
We have used some of these posts to build our list of alternatives
and similar projects. The last one was on 2020-10-07.
-
Building native images and compiling with GraalVM and sbt
For further investigation, I added the sbt-dependency-graph plugin and checked out the dependency-tree with sbt dependencyBrowserTree. The library logback wasn't included in the dependency tree. Which is odd, since logback is clearly present in the project's library-dependencies.
apply-at-vdb
Posts with mentions or reviews of apply-at-vdb.
We have used some of these posts to build our list of alternatives
and similar projects. The last one was on 2020-10-07.
-
Building native images and compiling with GraalVM and sbt
The full setup can be found on Github. But I'll summarise the used stack below. The project is built around the following libraries, no particular reason, simply because I like them.
What are some alternatives?
When comparing sbt-dependency-graph and apply-at-vdb you can also consider the following projects:
sbt-jib - sbt version of sbt jib: https://github.com/GoogleContainerTools/jib
sbt-assembly - Deploy über-JARs. Restart processes. (port of codahale/assembly-sbt)
unused-code - find and remove unused scala code
paradox - Markdown documentation
build-server-protocol - Protocol for IDEs and build tools to communicate about compile, run, test, debug and more.
scala-seed.g8 - A giter8 template for getting started with Scala 2.
giter8 - a command line tool to apply templates defined on GitHub
sbt-blowout - sbt plugin for generating configuration files
sbt-dependency-graph vs sbt-jib
apply-at-vdb vs sbt-assembly
sbt-dependency-graph vs unused-code
sbt-dependency-graph vs paradox
sbt-dependency-graph vs build-server-protocol
sbt-dependency-graph vs scala-seed.g8
sbt-dependency-graph vs sbt-assembly
sbt-dependency-graph vs giter8
sbt-dependency-graph vs sbt-blowout