You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I recently attempted to upgrade from Spring Boot 3.0.6 to 3.1.0, but encountered an incompatibility with FlyWay Enterprise 9.0.0 (the most recent version of this library). There's no mention in the release notes that this was an intentional breaking change, so I assume it was unintentional.
Application startup error:
***************************
APPLICATION FAILED TO START
***************************
Description:
An attempt was made to call a method that does not exist. The attempt was made from the following location:
org.springframework.boot.autoconfigure.flyway.FlywayAutoConfiguration$FlywayConfiguration.configureProperties(FlywayAutoConfiguration.java:248)
The following method did not exist:
'org.flywaydb.core.api.configuration.FluentConfiguration org.flywaydb.core.api.configuration.FluentConfiguration.executeInTransaction(boolean)'
Thanks for the report. I don't think cf95ae9 is the cause as it did not introduce the call to executeInTransaction. It was introduced in 238b85f in 3.1.0-M1. We can look at restoring compatibility with older versions of Flyway. In the future, it would also be much appreciated if you could test our milestones or even just release candidates so that we can catch this sort of problem before GA.
wilkinsona
changed the title
Spring Boot 3.1.0 incompatible with FlyWay Enterprise 9.0.0
Spring Boot 3.1.0 incompatible with Flyway 9.0
Jun 5, 2023
Cheers for the quick turnaround @wilkinsona . Sorry about the incorrect commit reference too. I just looked at the git blame for the tag and didn’t realise that the commit I referenced had just relocated the offending method (not introduced it).
I recently attempted to upgrade from Spring Boot 3.0.6 to 3.1.0, but encountered an incompatibility with FlyWay Enterprise 9.0.0 (the most recent version of this library). There's no mention in the release notes that this was an intentional breaking change, so I assume it was unintentional.
Application startup error:
Related commit:
cf95ae9
The text was updated successfully, but these errors were encountered: