Hm, I have complicated migrations I can't do from a sqm but need to do them in code. I did that by overwriting the schema, but now I lose all testing functionality.
I digged a bit in the source code and it seems that there the logic is already decoupled in the migration module but the logic for creating the statements from sql is deeply deeply integrated in the VerifyMigrationTask which I can't run from a junit test