Flyway V2 migration conflicts with casehub-qhorus V2 when both are on the same classpath

[mdproctor]

Problem

casehub-work ships a Flyway migration at version V2. casehub-qhorus also ships a Flyway migration at version V2. When both extensions are on the same classpath, Flyway finds two scripts at the same version and refuses to start:

FlywayException: Found more than one migration with version 2

Workaround (consumers)

Disable Flyway in tests and use drop-and-create:

quarkus.flyway.migrate-at-start=false
quarkus.flyway.qhorus.migrate-at-start=false
quarkus.hibernate-orm.database.generation=drop-and-create
quarkus.hibernate-orm.qhorus.database.generation=drop-and-create

Fix

Rename the casehub-work V2 migration to a version that does not conflict with casehub-qhorus, or use scoped Flyway migration locations. Coordinating with casehub-qhorus so both teams pick non-overlapping version ranges would be the cleaner solution.

References

• Companion issue on casehub-qhorus: Flyway V2 migration conflicts with casehub-work V2 when both are on the same classpath qhorus#142
• Discovered in Layer 1: naive Java investigation baseline (no CaseHub) aml#12