Flyway 5.0.7 warning about using schema_version table : <p>We use the Flyway Gradle plugin to do our migrations offline (i.e. we migrate while the system is down).  We recently upgraded to Flyway 5.0.7 and we see this warning now for migrations:</p>

<p><em>Could not find schema history table <code>XXXXXXX</code>.<code>flyway_schema_history</code>, but found <code>XXXXXXX</code>.<code>schema_version</code> instead. You are seeing this message because Flyway changed its default for flyway.table in version 5.0.0 to flyway_schema_history and you are still relying on the old default (schema_version). Set flyway.table=schema_version in your configuration to fix this. This fallback mechanism will be removed in Flyway 6.0.0.</em></p>

<p>(I've used the XXXXXXX to obscure the actual schema name).</p>

<p>So, it appears that we can avoid the error by setting flyway.table=schema_version.  But, it also says this mechanism will be removed in Flyway 6.0.0.</p>

<p>Are we supposed to do something to make this compatible going forward?  Do we have to manually rename the schema_version table to flyway_schema_history?  Or is there a way to make Flyway do it?  If not, what is going to happen when Flyway 6.0.0 comes out?  Will it automatically migrate the data to the appropriate table name?</p>
