title: Jgitver maven plugin: Always calculates -SNAPSHOT versions on tagged commits
body: <p>Here's what I do:</p>
  
  <ol>
  <li>I commit and push something</li>
  <li>I go to Github and create a release-tag on the latest commit on master, say 0.0.1</li>
  </ol>
  
  <p>Jenkins checks out branches <em>/tags/</em></p>
  
  <pre><code>Checking out Revision a499.......0e (refs/tags/0.0.1)
  </code></pre>
  
  <p>Jgitver claims:</p>
  
  <pre><code> [echo] Jgitver variables:
   [echo] jgitver.used_version: 0.0.1-SNAPSHOT
   [echo] jgitver.calculated_version: 0.0.1-SNAPSHOT
   [echo] jgitver.dirty: true
   [echo] jgitver.git_sha1_full: a499.......50e
   [echo] jgitver.branch_name: 
   [echo] jgitver.head_tags: 0.0.1
   [echo] jgitver.head_annotated_tags: 
   [echo] jgitver.head_lightweight_tags: 0.0.1
   [echo] jgitver.head_lightweight_tags: 0.0.1
   [echo] jgitver.all_tags: 0.0.1
   [echo] jgitver.all_annotated_tags: 
   [echo] jgitver.all_lightweight_tags: 0.0.1
   [echo] gitver.all_version_tags: 0.0.1
   [echo] jgitver.all_version_annotated_tags: 
   [echo] jgitver.all_version_lightweight_tags: 0.0.1
  </code></pre>
  
  <p>Jgitver config says:</p>
  
  <pre><code>&lt;mavenLike&gt;true&lt;/mavenLike&gt;
  
  &lt;autoIncrementPatch&gt;true&lt;/autoIncrementPatch&gt;
  
  &lt;useCommitDistance&gt;true&lt;/useCommitDistance&gt;
  
  &lt;useDirty&gt;false&lt;/useDirty&gt;
  
  &lt;useGitCommitId&gt;false&lt;/useGitCommitId&gt;
  
  &lt;gitCommitIdLength&gt;8&lt;/gitCommitIdLength&gt;
  
  &lt;nonQualifierBranches&gt;master&lt;/nonQualifierBranches&gt;
  
  &lt;useDefaultBranchingPolicy&gt;true&lt;/useDefaultBranchingPolicy&gt;
  </code></pre>
  
  <p>Same happens on the master branch. It never seems to build a 0.0.1, it will always build a 0.0.1-SNAPSHOT.</p>
  
  <p>I'm doing something wrong, but what is it?</p>