-
Notifications
You must be signed in to change notification settings - Fork 3k
Migration Guide 3.26
Note
|
We highly recommend the use of Items marked below with ⚙️ ✅ are automatically handled by |
As announced previously, we retired the legacy config classes support in 3.26. They were deprecated since 3.19.
This change should only affect extension maintainers.
-
@ConfigRoot
should exclusively be used on interfaces in conjunction with@ConfigMapping
- the deprecated attributes have also been removed -
@ConfigItem
has been dropped as it was only used for legacy config classes
The extension annotation processor will also complain with an error if it encounters a legacy config class.
The compatibility legacy config classes we kept in 3.19-3.25 are also gone:
-
GlobalDevServicesConfig
: useDevServicesConfig
instead -
HttpConfiguration
: useVertxHttpConfig
instead -
HttpBuildTimeConfig
: useVertxHttpBuildTimeConfig
instead
We recommend you base your extensions on 3.20 LTS now, and keep a maintenance branch for 3.15 LTS if you think it’s required for your extension.