Dependencies in Bleep are specified almost like in sbt, mill and so on
Java dependencies separate coordinate parts by colon (like sbt's
Scala dependencies use two colons after organization (similar to sbt's
Scala.js / Scala Native dependency
Surprise! These also use two colons, not three like in sbt.
But that's not like sbt does it!?
Bleep flips the default, the easiest syntax should be used for the most common thing.
If you want to add such a Scala JVM dependency to a JS/Native project, you can use the long form and a boolean flag
- forceJvm: true
As seen above, if you manually change this short form
to this long form:
- module: org.scala-sbt::librarymanagement-core:1.7.1
you can now tweak the dependency further.
You'll also get IDE support for navigating this:
Dependency upon sbt plugins
This lets you build sbt plugins with bleep (note that publishing is not implemented yet)
- isSbtPlugin: true
- configuration: provided
Note that Bleep has shed support for the most intricate ivyisms. What is left makes the structure much more cacheable, and should be enough for 99% of projects.