To smoothen the transition between Axon Framework 4 and 5, we should provide a dedicated legacy and/or migration module.
Axon Framework 4 currently has axon-legacy and axon-migration.
The former provides classes to support an upgrade from AF3 to AF4.
The latter was introduced for 4.7, providing an OpenRewrite migration recipe.
For AF5, I think it's fair to combine both the legacy and migration module in a single axon-migration module.
Things this module should (likely) contain are:
- An OpenRewrite migration script for (the majority of) the breaking changes between AF4 and AF5
- Utilities and other components to simplify the migration from AF4 to AF5. Examples of these utilities are the
QualifiedNameUtils and legacy handler registration tooling.
Milestone Note
Depending on how the development cycles proceeds, we may decide to move this issue to milestone 5.1.0. This potential shift is totally dependent on how much of the current AF4 features we are able to relay into AF5 features before our planned 5.0.0 release date. Since people that migrate may expect certain features from AF4 to be present in AF5, it is better to finalize a migration module once all (or at least the vast majority) of features have been adjusted to the new flow of AF5.
To smoothen the transition between Axon Framework 4 and 5, we should provide a dedicated legacy and/or migration module.
Axon Framework 4 currently has
axon-legacyandaxon-migration.The former provides classes to support an upgrade from AF3 to AF4.
The latter was introduced for 4.7, providing an OpenRewrite migration recipe.
For AF5, I think it's fair to combine both the legacy and migration module in a single
axon-migrationmodule.Things this module should (likely) contain are:
QualifiedNameUtilsand legacy handler registration tooling.Milestone Note
Depending on how the development cycles proceeds, we may decide to move this issue to milestone 5.1.0. This potential shift is totally dependent on how much of the current AF4 features we are able to relay into AF5 features before our planned 5.0.0 release date. Since people that migrate may expect certain features from AF4 to be present in AF5, it is better to finalize a migration module once all (or at least the vast majority) of features have been adjusted to the new flow of AF5.