-
Notifications
You must be signed in to change notification settings - Fork 2.7k
Migration Guide 2.5
We upgraded the Flyway dependency from 7.15 to version 8.0. Please refer to the Flyway release notes to see all the changes.
One important breaking change is that Flyway deprecated the Community support for database versions older than 5 years, for example: MySQL 5.7 and PostgreSQL 9.6. Therefore, users using the Flyway community and an unsupported database will have a failure at startup similar to:
Caused by: org.flywaydb.core.internal.license.FlywayEditionUpgradeRequiredException: Flyway Teams Edition or MySQL upgrade required:
MySQL 5.7 is no longer supported by Flyway Community Edition, but still supported by Flyway Teams Edition.
To avoid split packages, the following classes was deprecated in 2.1 and are now removed:
-
io.quarkus.hibernate.orm.panache.ProjectedFieldName
has been removed in favor ofio.quarkus.hibernate.orm.panache.common.ProjectedFieldName
.
To avoid split packages, the following classes was deprecated in 2.1 and are now removed:
-
io.quarkus.mongodb.panache.MongoEntity
has been removed in favor ofio.quarkus.mongodb.panache.common.MongoEntity
. -
io.quarkus.mongodb.panache.ProjectionFor
has been removed in favor ofio.quarkus.mongodb.panache.common.ProjectionFor
. -
io.quarkus.mongodb.panache.PanacheUpdate
has been removed in favor ofio.quarkus.mongodb.panache.common.PanacheUpdate
. -
io.quarkus.mongodb.panache.reactive.ReactivePanacheUpdate
has been removed in favor ofio.quarkus.mongodb.panache.common.reactive.ReactivePanacheUpdate
.
The quarkus-vertx
extension no longer depends on the quarkus-jackson
extension.
As a result, if your application depends on quarkus-vertx
and makes use of the io.vertx.core.json.JsonObject.mapFrom()
or the io.vertx.core.json.JsonObject.mapTo()
methods then the quarkus-jackson
extension should be added (either manually or as a transient dependency) to the project dependencies.