Wrong version when using git describe?

[jakobgrunig]

When I have git.useGitDescribe set to true I noticed the following:

1. I tag HEAD to 'v0.8.0' and 'sbt version' returns '0.8.0'
2. I commit something and 'sbt version' returns something like 'v0.8.0-1-gbeea47d'

Shouldn't this be '0.8.0-1-gbeea47d'?

[jsuereth]

probably, but I think we're using the "raw" git describe output. Would have to alter how we filter out the "v". Could be an easy fix if you're interested.

[charleskubicek]

Our current work-around is to override the gitDescribedVersion setting:

git.gitDescribedVersion <<= git.gitDescribedVersion((v) => v.map(_.drop(1)))

[metasim]

Scratch that... didn't fix the problem like I thought. something indeed appears to be getting cached.

My git version is 2.2.0.

I was having a similar problem but fixed it with this:

git.gitTagToVersionNumber := { tag: String =>
  if(tag matches "v[0.9]+\\..*") Some(tag.drop(1))
  else None
}

Wondering if something is funky with the default git.gitTagToVersionNumber function.

[metasim]

If I combine charleskubicek 's solution with overriding git.gitTagToVersionNumber, I get the behavior I'd expect.:

git.gitDescribedVersion <<= git.gitDescribedVersion((v) => v.map(_.drop(1)))

git.gitTagToVersionNumber := { tag: String =>
  if(tag matches "v[0.9]+\\..*") Some(tag.drop(1))
  else None
}

[dwijnand]

Fixed in #88