Building on the answer from @darko-cerdic
You can specify latest
as a revision number. Eg:
libraryDependencies += "org.apache.derby" % "derby" % "latest.release"
For more details check out ivy documentation:
http://ant.apache.org/ivy/history/2.3.0/ivyfile/dependency.html#revision
If you want, you can manually specify dependencyOverrides
to force a specific library version:
dependencyOverrides ++= Seq( "org.apache.derby" % "derby" % "1.0.0")
Note that in SBT 1.+ the dependencyOverrides are specified as a Seq, whereas in prior versions it was specified as a Set.
Using the sbt-lock plugin, you can lock the current version for all of your dependencies, so that your CI system can use a stable set of dependencies. It generates a set of dependencyOverrides
based on the current set of resolved libraryDependencies
. This gives you behavior that is similar to a Gemfile.lock.