Since the Java-based migrations are Spring Beans themselves, you can inject other beans. If those beans are somehow associated with JPA, the application fails on startup because a circular dependency ...

Hey, seems like you can create Spring Beans from Flyway Java-based migrations so that they're injected into the Flyway instance by Spring's DI mechanism, even though the migrations are located outside ...