AxonFramework-Full — migration pipeline
The Maven reactor is converted in dependency order — each phase only starts once everything it depends on is real. No phase is skipped ahead of the one before it, and nothing in a phase is bulk-copied; every file gets its own inspect-and-decide pass.
Repo bootstrap, license, root pom.xml conversion into
settings.gradle.kts + gradle.properties, versioning decided independently
of upstream.
Gradle's answer to axon-parent inheritance: the shared conventions
every module will apply.
Modules nothing else in the reactor depends on — safe to convert first.
test is grouped here by name only; it actually depends on axon-eventsourcing
(Phase 3) and can't safely start yet.
The framework's actual CQRS/event-sourcing machinery.
extensions sub-reactor
Not started
A nested reactor of its own, converted only once every core domain module it depends on exists.
Cross-module checks that only make sense once everything they cross exists.
Central Portal publishing and signing are already wired in the build-logic conventions — what's left is the coordinates that only make sense once everything above them is real.