title: Gradle Release Plugin for projects not following semantic versioning scheme
body: <p>I'm writing a components that will be working with some particular version of platform. Let's say the platform is in version 1.18.0, then I want to release component e.g. with version <code>1.18.0.1</code>, then <code>1.18.0.2</code>. If platform updates I want to release <code>1.19.0.1</code> etc. This of course breaks semantic versioning.</p>
  
  <p>I need a release plugin for Gradle, that supports this versioning scheme, but it uses only tags to store version (no commits during release, so I cannot use <a href="https://github.com/researchgate/gradle-release" rel="nofollow noreferrer">https://github.com/researchgate/gradle-release</a>).</p>
  
  <p>There are two plugins that from what I've seen enforce semantic versioning so I cannot use them:</p>
  
  <ul>
  <li>axion-release-plugin (<a href="https://github.com/allegro/axion-release-plugin" rel="nofollow noreferrer">https://github.com/allegro/axion-release-plugin</a>)</li>
  <li>nebula-release-plugin (<a href="https://github.com/nebula-plugins/nebula-release-plugin" rel="nofollow noreferrer">https://github.com/nebula-plugins/nebula-release-plugin</a>)</li>
  </ul>
  
  <p>How can I achieve basically the same as axion-release-plugin but with my custom versioning scheme that does not follow semver?</p>