title: Flyway customizing 'version' in naming convention
body: <p>I'm using Flyway 3.2.1. Current properties are set to:</p>
  
  <pre><code>flyway.sqlMigrationPrefix=V
  flyway.sqlMigrationSuffix=.sql
  flyway.initVersion=0000
  flyway.outOfOrder=false
  </code></pre>
  
  <p>According to the <a href="http://flywaydb.org/documentation/migration/" rel="nofollow noreferrer">documentation</a>, <strong>version</strong> can be:</p>
  
  <pre><code>Dots or underscores separate the parts, you can use as many parts as you like
  </code></pre>
  
  <p><a href="https://i.stack.imgur.com/sTJeU.png" rel="nofollow noreferrer"><img src="https://i.stack.imgur.com/sTJeU.png" alt="enter image description here"></a></p>
  
  <p>Therefore I came up with this <code>V_201509071234_Filename.sql</code>, even according to  <a href="http://flywaydb.org/documentation/migration/" rel="nofollow noreferrer">examples</a>, my name above should be valid. However when attempting to execute, it complains:</p>
  
  <blockquote>
    <p>Flyway Error: org.flywaydb.core.api.FlywayException: Invalid version
    containing non-numeric characters. Only 0..9 and . are allowed.
    Invalid version: .201509071234</p>
  </blockquote>
  
  <p>However, if I were to add a number before first underscore, like so,  <code>V2_201509071234_Filename.sql</code>, it works.</p>
  
  <p>How can I force Flyway to accept <code>V_201509071234_Filename.sql</code> as a valid name?</p>