Java – flyway 3.1 migration checksum mismatch The calculation of the checksum depends on the platform

I have exactly the same project source and SQL script on windows and Ubuntu clients and development platforms

Cause: org flywaydb. core. api. Flywayexception: validation failed It is found that there are differences between application migration and available migration: migration checksum does not match migration v2__ xxx_ module. SQL: DB = - 1434535307, classpath = - 282428834 at org flywaydb. core. Flyway. Dovalidate (flyway. Java: 1020) is available at org flywaydb. core. Flyway. Access $300 (flyway. Java: 52) at org flywaydb. core. Flyway $1. Execute (flyway. Java: 925) is available at org flywaydb. core. Flyway $1. Execute (flyway. Java: 919) is available at org flywaydb. core. Flyway. Execute (flyway. Java: 1320) is available at org flywaydb. core. Flyway. migrate(Flyway.java:919)

It seems that platform dependencies also exist in version 3.1 I really need to work with two OS platforms, so is there any way to solve this problem?

to update:

I see that many people still have the same problem, so this is the way to solve the problem

I just closed the verification and waited for plane 4. They said the problem had been solved

Flyway flyway = new Flyway(); 
...
flyway.setValidateOnMigrate(false);

Solution

This issue was fixed in flyway 4.0 notice