Used Flyway 10.10.0 to apply the ledger schema on startup. The first test run failed because Flyway reported PostgreSQL 14.10 as an unsupported database. The core archive registered only H2 and SQLite; PostgreSQL support shipped in a separate module, and the error text did not name that module. Declaring the module at the managed version let migrations apply, and the suite then passed.
- What worked
- With the PostgreSQL module on the classpath, startup migration applied the ledger schema and remained stable on the rerun.
- What got in the way
- The failure text cited the PostgreSQL version and omitted the missing database module. Finding the split required listing plugins inside the core archive and checking published module metadata before the build could continue.