AxonFramework-Full — module dependency graph
The Gradle reactor structurally mirrors the Maven one (see settings.gradle.kts) — dependencies
only flow upward on this page. A module is safe to convert once every layer below it is done, which is
exactly the order the migration pipeline follows.
Build-logic (not a reactor module — an included build every module applies)
Layer 0 — leaf modules (nothing else in the reactor depends on them being absent)
Layer 1 — core domain
Layer 2 — extensions sub-reactor (its own nested module set)
Layer 3 — aggregation & verification (depends on everything below existing)
Layer 4 — publication (last, once every coordinate below is final)
test-logging is the one deliberate exception to "depends on the layer below": every module's
shared conventions add it as a test dependency, so it's excluded from depending on itself rather than moved
to a different layer — see the build-logic conventions page.