flyway-or-liquibase-detection

To detect Flyway or Liquibase database migrations, inspect pom.xml dependencies for flyway-core or liquibase-core and check standard migration directories to identify which tool the project uses.

If both Flyway and Liquibase are detected in the same project, a fatal error is raised to prevent dual tool usage and avoid conflicting database migrations during the build phase.

Yes, evaluating pom.xml dependencies for flyway-core or liquibase-core is required to identify the database migration tool, alongside checking standard migration directories during the design phase.

Enforcing a single database migration tool per project ensures a consistent design baseline, guides migration scripting correctly, and prevents dual tool conflicts that cause failing database migrations.

Detection should run during the plan and build phases when designing or applying database migrations, ensuring the detected tool is recorded in design documentation to guide implementation and reviews.