This PR removes a feature introduced in summer '16 which allows to set Flyway's migration version at a central point, namely application.properties in the src/test/resources/config.
Without specifying a dedicated migration version, Flyway always uses its default migration version which is the highest available migration version in the directory defined by the property flyway.locations. This property is currently set in a decentralized per-test manner, i.e. it is set in a test class using the following annotation:
Example:
If the defined directory contains files named V0001__mydata.sql and V0002__myotherdata.sql the migration version is set to 2 and both scripts will be applied one after another (V0001 at first).
This PR removes a feature introduced in summer '16 which allows to set Flyway's migration version at a central point, namely
application.properties
in thesrc/test/resources/config
.Without specifying a dedicated migration version, Flyway always uses its default migration version which is the highest available migration version in the directory defined by the property
flyway.locations
. This property is currently set in a decentralized per-test manner, i.e. it is set in a test class using the following annotation:Example: If the defined directory contains files named
V0001__mydata.sql
andV0002__myotherdata.sql
the migration version is set to2
and both scripts will be applied one after another (V0001
at first).