Skip to content


Subversion checkout URL

You can clone with
Download ZIP
emulates Maven's uniqueVersion snapshots
Latest commit 62636ae @eed3si9n eed3si9n Merge pull request #4 from pdalpra/migrate-0.13
Migrate plugin to SBT 0.13 style
Failed to load latest commit information.
notes ls
project sbt 0.13
src/main Migrate plugin to 0.13 style
README.markdown readme
build.sbt sbt 0.13



sbt-unique-version emulates Maven's uniqueVersion snapshots on Ivy repos.


Try using git SHA. Josh Suereth in Effective sbt at Scala Days 2013 came up with an alternative approach. This could be the approach after sbt 0.13 and up.

val gitHeadCommitSha = settingKey[String]("current git commit SHA")

gitHeadCommitSha in ThisBuild := Process("git rev-parse HEAD").lines.head

version in ThisBuild := "1.0-" + gitHeadCommitSha.value


resolvers += Resolver.url("sbt-plugin-releases", url(""))(Resolver.ivyStylePatterns)

resolvers += Resolver.url("sbt-plugin-snapshots", url(""))(Resolver.ivyStylePatterns)

addSbtPlugin("com.eed3si9n" % "sbt-unique-version" % "latest.integration") // or "0.1.0"


Add the following in your build.sbt:

import UniqueVersionKeys._ // put this at the top


uniqueVersion := true

Set the version to a snapshot one such as "0.1.0-SNAPSHOT". This would substitute the artifact revision to something like "0.1.0-20120602-065305".

Optionally you can also specify the IvyStatus as follows:

ivyStatus <<= (version) { (v) =>
  if (v endsWith "-SNAPSHOT") IvyStatus.Integration
  else IvyStatus.Release

How to point at it

  • "0.1.0" or "0.1.0-20120602-073010" you can always use the static version number.
  • "0.1.0-+" selects the latest 0.1.0 snapshot.
  • "latest.integration" selects the latest revision regardless of its status.
  • "latest.milestone" selects the latest revision with either Milestone or Release status.
  • "latest.release" selects the latest with the Release status.

For example,

addSbtPlugin("com.eed3si9n" % "sbt-unique-version" % "0.1.0-+")

This adds the latest 0.1.0 snapshot of sbt-unique-version to your build.

What's the point of this?

The current way sbt does the snapshots is to overwrite the jar file with the same resolution URL. That is a cause of several issues like caching issues and security settings at the repository.


Unlike Maven's uniqueVersion, or just plain "x.x.x-SNAPSHOT", this approach takes over the revision.

Something went wrong with that request. Please try again.