-
Notifications
You must be signed in to change notification settings - Fork 2.9k
Migration Guide 1.4
If you are specifying extra JVM arguments in quarkusDev
task, you need to change from:
tasks.withType(QuarkusDev) {
jvmArgs = "-Djavax.net.ssl.keyStore=/path/to/keystores/keystore.jks -Djavax.net.ssl.keyStorePassword=password"
}
to:
tasks.withType(QuarkusDev) {
jvmArgs = ["-Djavax.net.ssl.keyStore=/path/to/keystores/keystore.jks", "-Djavax.net.ssl.keyStorePassword=password"]
}
We have deprecated the ./gradlew buildNative
task in favor of ./gradlew build -Dquarkus.package.type=native
. If your build still uses buildNative
you should see the following warning message:
The 'buildNative' task has been deprecated in favor of 'build -Dquarkus.package.type=native'
The Kogito extension has been moved out of the Core repository: it is now part of the Quarkus Platform.
The GA has changed so you should use org.kie.kogito:kogito-quarkus
instead of io.quarkus:quarkus-kogito
.
Configuration properties relative to Elasticsearch index lifecycle management have changed. See this section of the reference documentation for detailed documentation about schema management.
In short:
-
quarkus.hibernate-search.elasticsearch.index_defaults.lifecycle.strategy
is nowquarkus.hibernate-search.schema-management.strategy
and accepts the same values as before:none
,create
,validate
,update
, ... - A new schema management strategy on startup was introduced:
create-or-validate
. It create indexes if they don't exist, validates their schema if they already exist. - The default schema management strategy on startup is now
create-or-validate
. -
quarkus.hibernate-search.elasticsearch.index_defaults.lifecycle.required_status
is nowquarkus.hibernate-search.elasticsearch.index_defaults.schema_management.required_status
. -
quarkus.hibernate-search.elasticsearch.index_defaults.lifecycle.required_status_wait_timeout
is nowquarkus.hibernate-search.elasticsearch.index_defaults.schema_management.required_status_wait_timeout
.
Also related: you can now use SearchSchemaManager
APIs
to trigger schema management operations at the time of your choosing (not just on startup).