Non-transactional Java-based migrations support

[axelfontaine]

Until now JdbcMigration and SpringJdbcMigration implementations could only execute within a transaction. Flyway 5.2.0 introduces a new JavaMigration type which supersedes both existing ones and additionally can be configured to optionally execute without a transaction.

[geoffreywiseman]

Is there documentation describing the best upgrade approach for people with SpringJdbcMigrations? I've seen some examples like this, using a SingleConnectionDataSource:
https://stackoverflow.com/questions/53722392/flyway-how-to-replace-deprecated-springjdbcmigration-without-getting-flywayexc

From the looks of things that's pretty close to what Flyway does internally.

I'm just trying to understand the upgrade path for people who have some SpringJdbcMigration descendants, and what the recommendation is on how to modify those classes. Is it just that Spring JdbcTemplate support is gone, isn't returning, there will be no guidance and people can do whatever they want to bridge that gap? Or is it something else -- something that's coming, or something that I haven't found?